From e86f3b5ca5197251c4d1ddcf2a3a80a09fd5dfcb Mon Sep 17 00:00:00 2001 From: Fen Labalme Date: Tue, 19 Mar 2024 14:25:33 -0400 Subject: [PATCH] initial updates --- .DS_Store | Bin 8196 -> 0 bytes CNAME | 2 +- _config.yml | 6 +- _data/.DS_Store | Bin 6148 -> 0 bytes _data/footer.yml | 4 +- _data/header.yml | 5 +- _guide/.DS_Store | Bin 6148 -> 0 bytes _guide/introduction.md | 4 +- _includes/.DS_Store | Bin 6148 -> 0 bytes _layouts/.DS_Store | Bin 6148 -> 0 bytes _layouts/guide.html | 4 +- _people/.DS_Store | Bin 6148 -> 0 bytes _people/fen-labalme.md | 5 +- _people/luke-fretwell.md | 19 - _people/marlena-medford.md | 19 - _posts/.DS_Store | Bin 6148 -> 0 bytes _posts/2021-02-19-hello-world.md | 6 +- ...lly-fix-the-security compliance problem.md | 2 +- ...urity-with-a-federal-compliance-library.md | 2 +- _posts/2024-03-11-cybersecurity-notes.md | 17 + _sass/uswds/.DS_Store | Bin 6148 -> 0 bytes _site/404.html | 17 +- _site/CNAME | 2 +- _site/README.md | 4 +- _site/about.html | 27 +- _site/accessibility.html | 23 +- _site/assets/img/logos/OpenATO.png | Bin 0 -> 6998 bytes _site/colophon.html | 17 +- _site/conduct.html | 39 +- _site/contact.html | 19 +- _site/federal-compliance-library.html | 17 +- _site/guide.html | 24 +- _site/guide/introduction.html | 22 +- _site/guide/problem.html | 20 +- _site/guide/resources.html | 20 +- _site/guide/solution.html | 20 +- _site/guide/stakeholders.html | 20 +- _site/index.html | 65 +-- _site/join.html | 23 +- _site/license.html | 21 +- _site/news/index.html | 28 +- _site/open.html | 23 +- _site/people.html | 58 +-- _site/people/fen-labalme.html | 21 +- _site/people/marlena-medford.html | 408 ------------------ _site/people/mary-lazzeri.html | 17 +- _site/playbook.html | 19 +- .../cybersecurity-notes.html} | 106 +++-- _site/posts/day-one-project.html | 17 +- ...y-fix-the-security-compliance-problem.html | 19 +- ...ity-with-a-federal-compliance-library.html | 17 +- ...hinking-the-process-of-attaining-atos.html | 17 +- _site/posts/hello-world.html | 20 +- _site/sitemap.xml | 64 ++- assets/.DS_Store | Bin 6148 -> 0 bytes assets/img/.DS_Store | Bin 8196 -> 0 bytes assets/img/cards/.DS_Store | Bin 6148 -> 0 bytes assets/img/circles/.DS_Store | Bin 6148 -> 0 bytes assets/img/icons/18F_feather/all/.DS_Store | Bin 6148 -> 0 bytes assets/img/logos/.DS_Store | Bin 6148 -> 0 bytes assets/img/logos/OpenATO.png | Bin 0 -> 6998 bytes assets/img/people/.DS_Store | Bin 6148 -> 0 bytes assets/uswds/.DS_Store | Bin 6148 -> 0 bytes assets/uswds/img/favicons/.DS_Store | Bin 6148 -> 0 bytes assets/uswds/img/social-icons/.DS_Store | Bin 6148 -> 0 bytes news/index.html | 4 +- pages/#about.md# | 14 + pages/.#about.md | 1 + pages/.DS_Store | Bin 6148 -> 0 bytes pages/about.md | 8 +- pages/accessibility.md | 6 +- pages/conduct.md | 22 +- pages/contact.md | 2 +- pages/guide.html | 8 +- pages/home.md | 10 +- pages/join.md | 4 +- pages/license.md | 4 +- pages/open.md | 6 +- pages/people.html | 6 +- pages/playbook.html | 4 +- 80 files changed, 563 insertions(+), 865 deletions(-) delete mode 100644 .DS_Store delete mode 100644 _data/.DS_Store delete mode 100644 _guide/.DS_Store delete mode 100644 _includes/.DS_Store delete mode 100644 _layouts/.DS_Store delete mode 100644 _people/.DS_Store delete mode 100644 _people/luke-fretwell.md delete mode 100644 _people/marlena-medford.md delete mode 100644 _posts/.DS_Store create mode 100644 _posts/2024-03-11-cybersecurity-notes.md delete mode 100644 _sass/uswds/.DS_Store create mode 100644 _site/assets/img/logos/OpenATO.png delete mode 100644 _site/people/marlena-medford.html rename _site/{people/luke-fretwell.html => posts/cybersecurity-notes.html} (65%) delete mode 100644 assets/.DS_Store delete mode 100644 assets/img/.DS_Store delete mode 100644 assets/img/cards/.DS_Store delete mode 100644 assets/img/circles/.DS_Store delete mode 100644 assets/img/icons/18F_feather/all/.DS_Store delete mode 100644 assets/img/logos/.DS_Store create mode 100644 assets/img/logos/OpenATO.png delete mode 100644 assets/img/people/.DS_Store delete mode 100644 assets/uswds/.DS_Store delete mode 100644 assets/uswds/img/favicons/.DS_Store delete mode 100644 assets/uswds/img/social-icons/.DS_Store create mode 100644 pages/#about.md# create mode 120000 pages/.#about.md delete mode 100644 pages/.DS_Store diff --git a/.DS_Store b/.DS_Store deleted file mode 100644 index 0b5b10bde73f851ff7d7d7caa8782dcb1905c84f..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 8196 zcmeHMziSjh6n>Lm-eF_s8KZ1rBc|{`5h2ByoJpw=EJQ>vIgJOK?7=03SjaYKVIfwc zRV=La9}pB93ky?PSSV;=cVJ;9_`R87@6GJ)*@==F*m=jk@6G%6o7vfYdqkw>x7u~0 z8WB}+usw7TT|r|%AGtPW&&+zQ)BhkflikIuoF0~8-Ak>&@qv<4Qo?lbtuL()q}F3 z%9a?)gu@>(9JXO?YODz-Wx`3>%*s|MN@qu0q~W9*#)dv95ERHOz_t4%-JmwLXw$FX z&%JlO>q)b@5+^G-Tee~q@N0~WX3F9@~1@0T3Z z{q0YdgEPi@GGtMPae16(9#!z@&<3qi3^w3GJ(tbysbZAmba-y&gXL5(o@6!}>F`sZ znO_C`V$9PHCE&N|vs>6J!bom=uV1~f+;U?{W}|QpFM7nh4uDq|Y9;7ne+G{-D-R(# zElw|7ubXw0Lk(xK9Od%4%zSt)bit;V*Xa1J@0VPDz3g8*Yq&ULNNvh61w8n^>S4Zm z-b__@I$$BZk^@mXHv2rguWYgW$A9;oZHbVz0ICqt59XsQCW&SHO_kKM1De~)h znZFnz^Q$j^9gEx!~aM<={ zfmBucWd5fQ=dKQ3==@o%RG`Q&^V)ZyNvy&acDCF;vUDDqg;(ajl=Pou`)U?1vlk=W z`~$x3(1HS^6c{(o8rT09%fJ7R8Y1|D0zrZQTmd!FTyDBeu7~*#XD91FcO^wAFw7>o#Ap3VRJpc6sgl=Cd@Edgiqlo|j diff --git a/CNAME b/CNAME index 5a16f74..9ad4dc8 100644 --- a/CNAME +++ b/CNAME @@ -1 +1 @@ -atoasap.org \ No newline at end of file +openato.org diff --git a/_config.yml b/_config.yml index 15b3934..a40a908 100644 --- a/_config.yml +++ b/_config.yml @@ -1,4 +1,4 @@ -title: ATO ASAP +title: OpenATO description: # baseurl: /compliance-as-code # the subpath of your site, e.g. /blog # url: https://govthinktank.github.io/compliance-as-code/ # the base hostname & protocol for your site, e.g. http://example.com @@ -6,10 +6,10 @@ description: # GitHub information # This is used for adding an edit this page link to the footer github_info: - organization: ato-asap + organization: openato repository: website -url: "https://ato-asap.github.io" # the base hostname & protocol for your site +url: "https://openato.github.io" # the base hostname & protocol for your site plugins: - jekyll-sitemap - jekyll-redirect-from diff --git a/_data/.DS_Store b/_data/.DS_Store deleted file mode 100644 index 5008ddfcf53c02e82d7eee2e57c38e5672ef89f6..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 6148 zcmeH~Jr2S!425mzP>H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0
  • - ATO ASAP Guide + OpenATO Guide
  • @@ -36,4 +36,4 @@

    {{ page.title }}

    - \ No newline at end of file + diff --git a/_people/.DS_Store b/_people/.DS_Store deleted file mode 100644 index 5008ddfcf53c02e82d7eee2e57c38e5672ef89f6..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 6148 zcmeH~Jr2S!425mzP>H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0H1@V-^m;4Wg<&0T*E43hX&L&p$$qDprKhvt+--jT7}7np#A3 zem<@ulZcFPQ@L2!n>{z**++&mCkOWA81W14cNZlEfg7;MkzE(HCqgga^y>{tEnwC%0;vJ&^%eQ zLs35+`xjp>T0 If we collaborate and take deliberate steps to integrate automation, we can unlock the bureaucratic inertia that has stalled compliance modernization and fix the ATO problem once and for all. -Full post: [ATO ASAP: Let’s finally fix the security compliance problem](https://fcw.com/articles/2021/02/04/comment-lazzeri-automate-ato.aspx) \ No newline at end of file +Full post: [ATO ASAP: Let’s finally fix the security compliance problem](https://www.nextgov.com/modernization/2021/02/ato-asap-lets-finally-fix-the-security-compliance-problem/258357/) diff --git a/_posts/2021-03-22-fcw-streamlining-government-security-with-a-federal-compliance-library.md b/_posts/2021-03-22-fcw-streamlining-government-security-with-a-federal-compliance-library.md index 2b9b384..c67464d 100644 --- a/_posts/2021-03-22-fcw-streamlining-government-security-with-a-federal-compliance-library.md +++ b/_posts/2021-03-22-fcw-streamlining-government-security-with-a-federal-compliance-library.md @@ -16,4 +16,4 @@ From the post: > By building a Federal Compliance Library based on open, iterative, collaborative principles, the federal government technology community will go further, faster. -Full post: [ATO ASAP: Streamlining government security with a Federal Compliance Library](https://fcw.com/articles/2021/03/22/comment-lazzeri-ato-asap.aspx) \ No newline at end of file +Full post: [ATO ASAP: Streamlining government security with a Federal Compliance Library](https://fcw.com/articles/2021/03/22/comment-lazzeri-ato-asap.aspx) diff --git a/_posts/2024-03-11-cybersecurity-notes.md b/_posts/2024-03-11-cybersecurity-notes.md new file mode 100644 index 0000000..27a618e --- /dev/null +++ b/_posts/2024-03-11-cybersecurity-notes.md @@ -0,0 +1,17 @@ +--- +layout: post +title: "Cybersecurity: Open and Transparent" +date: 2024-03-11 08:00:00 -0800 +description: Data Centricity is key. +author: fen-labalme +categories: featured +image: card-power.png +--- + +Obtaining an ATO is required for every internet-based system in the federal government. The documentation for an ATO is called a system security plan or SSP. Creating the SSP can take months, and very few SSPs are clear, complete or well written. In particular, details about how, say, access control or audit logs are managed may be broadly covered with few specifics regarding the system at hand. Further complicating the process, is a shroud of secrecy that forces every ISSO building a SSP has to reinvent the wheel for every technology component that their system is using. + +After inspecting hundreds of SSPs, we have found that the information contained within rarely requires secrecy to maintain the security of the system. And when such sensitive information exists it is usually misplaced and should not be in the SSP to begin with. To be clear, the results of assessing an SSP, that may include a list of discovered vulnerabilities, can reasonably be considered sensitive and maintained in a secure fashion. But there's a little reason for the SSP itself to remain secret, or even for the secure management of the general component-level assessment processes. (Tailored, specific assessment processes aimed at a particular implementation and environment may be crafted to exercise specific features of a system, and therefore may have a need to remain secret. But this is the exception and not the rule.) + +The threat landscape is evolving along with Moore's Law at an exponential rate. Humans do not evolve so quickly. And there is an increasing need to be proactive in the expanding open source software world. SBOM can show you CVEs that exist, but you need to know, your developers need to know what the risks are and what needs to be protected and what the business case is. Where open source development appears to be getting more opaque, we believe this is the perfect time to introduce open source assessment and open source ATOs. + +Creating an SSP in an open and transparent manner can help to improve communication and collaboration between different parts of an organization and even across orgaanizations. A library of separable, reusable components enables wide review and support to address changes in the threat landscape existing security vulnerabilities that might otherwise have been overlooked. diff --git a/_sass/uswds/.DS_Store b/_sass/uswds/.DS_Store deleted file mode 100644 index a89b55b3df46b2006f01ec0e051677c013ef8889..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 6148 zcmeHKOHRWu5FNJ>DrM7UcjN$UDlQPJzy*2%)E1RW4XJ3m&k;BT2jC2xhBL6@%|{U? zwZsYmnyEa`nHk$JPl{a=QJ5Z<6QU6j4bT{~A>0w;JhzVZEW(3>%u&+=-J$Ji*Qxe^ zE8q(JHU;?G9nykos%Q(}e!rX5WVWcQtr9+ePt{d*SUKP4D9Q^(tMv{C4g3 z{`2}TOydMR57=4u%r@qi-F(d_ctvwm^-(@iP0WMk!h7zp%kA-7L$4L>VlG_Ltx53d z%$4BOsf&5Zntkwkq(#K$^zsck%Op6o*`sP$Hd=4|Bn!Ix(+c3sW*eL-x_1R!0au_^ zfcJ+Sjj=Fn6lLpxlPdr)Ls$%bIU|8N2Y`iPqlgGB=un^z4R*x{Ivnxb>I%a~QHN8I zl`)U49PEY?WOc-IDW^~ -Not found (404) | ATO ASAP +Not found (404) | OpenATO @@ -68,8 +68,13 @@ href="/" title="Home"> + OpenATO + - ATO ASAP ALPHA + OpenATO ALPHA @@ -224,11 +229,11 @@

    Not found (404)

    -Help improve this page +Help improve this page

    @@ -320,7 +325,7 @@

    Not found (404)

    - +
    @@ -332,7 +337,7 @@ @@ -343,7 +350,7 @@ @@ -369,7 +374,7 @@ @@ -343,7 +348,7 @@
    -

    The ATO ASAP community is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of participants in any form.

    +

    The OpenATO community is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of participants in any form.

    -

    This code of conduct applies to all ATO ASAP sponsored spaces, including our blog, mailing lists, and wiki, as well as any other spaces that ATO ASAP hosts, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the ATO ASAP Anti-Abuse Team.

    +

    This code of conduct applies to all OpenATO sponsored spaces, including our blog, mailing lists, and wiki, as well as any other spaces that OpenATO hosts, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the OpenATO Anti-Abuse Team.

    -

    Some ATO ASAP-sponsored spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and abiding by these rules. +

    Some OpenATO-sponsored spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and abiding by these rules. Definitions

    Harassment includes:

    @@ -231,11 +236,11 @@

    Code of conduct

  • Unwelcome sexual attention
  • Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
  • Continued one-on-one communication after requests to cease
  • -
  • Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect other ATO ASAP members or other vulnerable people from intentional abuse
  • +
  • Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to protect other OpenATO members or other vulnerable people from intentional abuse
  • Publication of non-harassing private communication
  • -

    The ATO ASAP community prioritizes marginalized people’s safety over privileged people’s comfort. The ATO ASAP Anti-Abuse Team will not act on complaints regarding:

    +

    The OpenATO community prioritizes marginalized people’s safety over privileged people’s comfort. The OpenATO Anti-Abuse Team will not act on complaints regarding:

    • ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ (because these things don’t exist)
    • @@ -247,18 +252,18 @@

      Code of conduct

      Reporting

      -

      If you are being harassed by a member of the ATO ASAP community, notice that someone else is being harassed, or have any other concerns, please contact the ATO ASAP Anti-Abuse Team. If the person who is harassing you is on the team, they will recuse themselves from handling your incident. We will respond as promptly as we can.

      +

      If you are being harassed by a member of the OpenATO community, notice that someone else is being harassed, or have any other concerns, please contact the OpenATO Anti-Abuse Team. If the person who is harassing you is on the team, they will recuse themselves from handling your incident. We will respond as promptly as we can.

      -

      This code of conduct applies to ATO ASAP sponsored spaces, but if you are being harassed by a member of the ATO ASAP community outside our spaces, we still want to know about it. We will take all good-faith reports of harassment by ATO ASAP community members, especially bloggers, seriously. This includes harassment outside our spaces and harassment that took place at any point in time.The abuse team reserves the right to exclude people from the ATO ASAP community based on their past behavior, including behavior outside ATO ASAP spaces and behavior towards people who are not in the ATO ASAP community.

      +

      This code of conduct applies to OpenATO sponsored spaces, but if you are being harassed by a member of the OpenATO community outside our spaces, we still want to know about it. We will take all good-faith reports of harassment by OpenATO community members, especially bloggers, seriously. This includes harassment outside our spaces and harassment that took place at any point in time.The abuse team reserves the right to exclude people from the OpenATO community based on their past behavior, including behavior outside OpenATO spaces and behavior towards people who are not in the OpenATO community.

      -

      In order to protect volunteers from abuse and burnout, we reserve the right to reject any report we believe to have been made in bad faith. The ATO ASAP Anti-Abuse Team is not here to explain power differentials or other basic social justice concepts to you. Reports intended to silence legitimate criticism may be deleted without response.

      +

      In order to protect volunteers from abuse and burnout, we reserve the right to reject any report we believe to have been made in bad faith. The OpenATO Anti-Abuse Team is not here to explain power differentials or other basic social justice concepts to you. Reports intended to silence legitimate criticism may be deleted without response.

      -

      We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of ATO ASAP members or the general public. We will not name harassment victims without their affirmative consent. +

      We will respect confidentiality requests for the purpose of protecting victims of abuse. At our discretion, we may publicly name a person about whom we’ve received harassment complaints, or privately warn third parties about them, if we believe that doing so will increase the safety of OpenATO members or the general public. We will not name harassment victims without their affirmative consent. Consequences

      Participants asked to stop any harassing behavior are expected to comply immediately.

      -

      If a participant engages in harassing behavior, the ATO ASAP Anti-Abuse Team may take any action they deem appropriate, up to and including expulsion from all ATO ASAP spaces and identification of the participant as a harasser to other ATO ASAP members or the general public.

      +

      If a participant engages in harassing behavior, the OpenATO Anti-Abuse Team may take any action they deem appropriate, up to and including expulsion from all OpenATO spaces and identification of the participant as a harasser to other OpenATO members or the general public.

      @@ -283,11 +288,11 @@

      Code of conduct

      -Help improve this page +Help improve this page

      @@ -379,7 +384,7 @@

      Code of conduct

      - +
      @@ -391,7 +396,7 @@ @@ -339,7 +344,7 @@ @@ -386,7 +391,7 @@
    + @@ -323,11 +329,11 @@

    Resources

    -Help improve this page +Help improve this page

    @@ -419,7 +425,7 @@

    Resources

    - +
    @@ -431,7 +437,7 @@ + @@ -286,11 +292,11 @@

    Introduction

    -Help improve this page +Help improve this page

    @@ -382,7 +388,7 @@

    Introduction

    - +
    @@ -394,7 +400,7 @@ + @@ -294,11 +300,11 @@

    Problem

    -Help improve this page +Help improve this page

    @@ -390,7 +396,7 @@

    Problem

    - +
    @@ -402,7 +408,7 @@ + @@ -287,11 +293,11 @@

    Resources

    -Help improve this page +Help improve this page

    @@ -383,7 +389,7 @@

    Resources

    - +
    @@ -395,7 +401,7 @@ + @@ -284,11 +290,11 @@

    Solution

    -Help improve this page +Help improve this page

    @@ -380,7 +386,7 @@

    Solution

    - +
    @@ -392,7 +398,7 @@ + @@ -299,11 +305,11 @@

    Stakeholders

    -Help improve this page +Help improve this page

    @@ -395,7 +401,7 @@

    Stakeholders

    - +
    @@ -407,7 +413,7 @@ @@ -260,7 +265,7 @@

    Project board

    Contribute

    Contribute

    -

    Everyone is welcome. Learn how you can contribute to ATO ASAP.

    +

    Everyone is welcome. Learn how you can contribute to OpenATO.

    @@ -300,42 +305,6 @@

    Fen Labalme

    -
  • -
    -
    -
    - Luke Fretwell -
    -
    -
    -

    Luke Fretwell

    -
    -
    -

    -
    - -
    -
  • - -
  • -
    -
    -
    - Marlena Medford -
    -
    -
    -

    Marlena Medford

    -
    -
    -

    -
    - -
    -
  • -
  • @@ -361,6 +330,10 @@

    Mary Lazzeri

    News

    +

    Cybersecurity: Open and Transparent

    +

    Data Centricity is key.

    +

    March 11, 2024

    +

    FCW: Streamlining government security with a Federal Compliance Library

    FCW published a guest editorial we wrote on building a Federal Compliance Library to help streamline the authority to operate process.

    March 22, 2021

    @@ -382,7 +355,7 @@

    Day One Project: Compliance as Code and Imp

    Get started

    -

    Learn and contribute to ATO ASAP.

    +

    Learn and contribute to OpenATO.

    Join us

    @@ -404,11 +377,11 @@

    Get started

    -Help improve this page +Help improve this page

    @@ -500,7 +473,7 @@

    Get started

    - +
    @@ -512,7 +485,7 @@

    @@ -338,7 +343,7 @@ @@ -336,7 +341,7 @@
    @@ -247,11 +257,11 @@

    Day One Project: Compliance as Code and Imp -Help improve this page +Help improve this page

    @@ -343,7 +353,7 @@

    Day One Project: Compliance as Code and Imp
    - +

    @@ -355,7 +365,7 @@ @@ -344,7 +351,7 @@
  • -
  • -
    -
    -
    - Luke Fretwell -
    -
    -
    -

    Luke Fretwell

    -
    -
    -

    -
    - -
    -
  • - -
  • -
    -
    -
    - Marlena Medford -
    -
    -
    -

    Marlena Medford

    -
    -
    -

    -
    - -
    -
  • -
  • @@ -290,6 +259,7 @@

    Mary Lazzeri

    + @@ -307,11 +277,11 @@

    Mary LazzeriHelp improve this page +Help improve this page

    @@ -403,7 +373,7 @@

    Mary Lazzeri -

    + @@ -415,7 +385,7 @@
  • LinkedIn
  • -
  • Twitter
  • +
  • GitLab
  • @@ -224,6 +229,8 @@

    Connect

    Posts

    @@ -251,11 +258,11 @@

    Posts

    -Help improve this page +Help improve this page

    @@ -347,7 +354,7 @@

    Posts

    - +
    @@ -359,7 +366,7 @@ @@ -253,11 +258,11 @@

    Posts

    -Help improve this page +Help improve this page

    @@ -349,7 +354,7 @@

    Posts

    - +
    @@ -361,7 +366,7 @@ @@ -335,7 +340,7 @@ @@ -352,7 +376,7 @@ @@ -366,7 +371,7 @@ @@ -264,11 +269,11 @@

    FCW: ATO ASAP: Let’s finally fix the security com -Help improve this page +Help improve this page

    @@ -360,7 +365,7 @@

    FCW: ATO ASAP: Let’s finally fix the security com
    - +
    @@ -372,7 +377,7 @@

    @@ -376,7 +381,7 @@ @@ -366,7 +371,7 @@ @@ -372,7 +378,7 @@ \ No newline at end of file + diff --git a/pages/playbook.html b/pages/playbook.html index 38ddd65..edcc948 100644 --- a/pages/playbook.html +++ b/pages/playbook.html @@ -1,13 +1,13 @@ --- layout: default -title: ATO ASAP Playbook +title: OpenATO Playbook description: excerpt: permalink: /playbook hero: image: callout: - alt: "ATO ASAP Playbook" + alt: "OpenATO Playbook" text: link: text: Link to more about that priority