{"id":280,"date":"2022-09-24T18:32:56","date_gmt":"2022-09-24T18:32:56","guid":{"rendered":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/?p=280"},"modified":"2022-09-25T13:25:30","modified_gmt":"2022-09-25T13:25:30","slug":"the-nist-cybersecurity-framework","status":"publish","type":"post","link":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/2022\/09\/24\/the-nist-cybersecurity-framework\/","title":{"rendered":"The NIST Cybersecurity Framework"},"content":{"rendered":"Organizations are guaranteed a reliable and well-developed system that has\nyet to serve its on lookers. The first benefit lives in the nature of the\ncoding software. As time goes on, there are new developments to be processed\nand people all around hoping to snag information. This is one of the many\nbenefits that the NIST framework sees fit to fixing. Another benefit has to do\nwith the seamless execution that the framework provides. The framework is split\nup into three different sections, which consist of the Framework core,\nImplementation tiers, and the Framework profiles. Each of these distinct\ncategories are special in their own way and operate in the background.\n\n<!-- \/wp:paragraph --><!-- wp:paragraph -->\n\nFor example, the core is responsible for providing a set of activities that\nit will use to achieve specific outcomes. The five main cores to remember are\ndetect, identify, protect, respond, and recover. The Implementation tiers on\nthe other hand, are responsible for providing the necessary context on how an\norganization views the risk involved with cybersecurity as well as the\nprocesses in place to counteract the risk. Thirdly, the Cybersecurity framework\nis adaptable to every single issue and task that it meets. Due to continuous\nand ongoing advancements regarding technology and devices, different forms of\ninfrastructures are needed for certain tasks. Thankfully the NIST framework is\na reliable solution. Lastly, the ease of use that NIST frameworks provide is\nreassuring to current business owners due to the simplicity behind it all.\n\n<!-- \/wp:paragraph --><!-- wp:paragraph -->\n\nTo setup a new program or improve on an existing one, companies can utilize\nthe seven steps of prioritizing and scope, orient, create a profile, risk\nassessment, target profile creation, analyzing gaps, and implementing the\nentirety of the action. The first step would be for identifying the issue at\nhand before continuing. The second step comes after the planning and requires\nthe individuals to find and collect the necessary tools to continue forth with\ntheir plan. The third step is for creating a profile that suits the needs of\nthe company. The fourth is an assessment involving risk management. The fifth\nstep can be seen as a storing and cleaning step since it separates everything\ninto framework categories and subcategories. As far as step six, deterring,\nanalyzing, and prioritizing gaps are its main steps. It can be looked at as the\nfinal planning and cost summation of it all. Lastly, step 7 would be used to\nput all the steps into play by implementing the action.\n\n<!-- \/wp:paragraph --><!-- wp:paragraph -->\n\nWith a careful and well thought out adoption of the seven steps, companies\nshould find the creation of a framework to be a breeze. If I were to\nincorporate a Cybersecurity Framework into my line of work in the future, I\nwould do it by incorporating the seven steps. I would also brush up on the\ninformation and collaborate with fellow workers to decide on the best possible\nsolution. After my decision and setup of the framework, I see nothing but\nsmooth sailing after that regarding the startup, continuation, and\nresponsibilities of the framework.\n\n<!-- \/wp:paragraph -->","protected":false},"excerpt":{"rendered":"<p>Organizations are guaranteed a reliable and well-developed system that has yet to serve its on lookers. The first benefit lives in the nature of the coding software. As time goes on, there are new developments to be processed and people all around hoping to snag information. This is one of the many benefits that the&#8230; <\/p>\n<div class=\"link-more\"><a href=\"https:\/\/sites.wp.odu.edu\/spencer-foulk\/2022\/09\/24\/the-nist-cybersecurity-framework\/\">Read More<\/a><\/div>\n","protected":false},"author":24957,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","wds_primary_category":0},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/posts\/280"}],"collection":[{"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/users\/24957"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/comments?post=280"}],"version-history":[{"count":3,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/posts\/280\/revisions"}],"predecessor-version":[{"id":285,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/posts\/280\/revisions\/285"}],"wp:attachment":[{"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/media?parent=280"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/categories?post=280"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.wp.odu.edu\/spencer-foulk\/wp-json\/wp\/v2\/tags?post=280"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}