{"id":221,"date":"2015-02-13T21:00:01","date_gmt":"2015-02-13T21:00:01","guid":{"rendered":"http:\/\/cybersecurity.bellevue.edu\/?p=221"},"modified":"2018-07-25T08:14:39","modified_gmt":"2018-07-25T14:14:39","slug":"loose-lips-might-sink-ships","status":"publish","type":"post","link":"https:\/\/cybersecurity.bellevue.edu\/index.php\/2015\/02\/13\/loose-lips-might-sink-ships\/","title":{"rendered":"Loose Lips Might Sink Ships"},"content":{"rendered":"<p>Are you watching what you are telling your neighbors?\u00a0 Do you guard information in your care to make sure only those people with a need to know can see it? Hopefully, you\u2019re not accidentally letting any secrets slip.\u00a0 It could be disastrous if confidential information got out to your competitors.\u00a0 It could hurt your sales, your stock price and your reputation.<\/p>\n<p>It happens in a variety of ways: accidental disclosure, carelessness in storage and protection, and corporate espionage.\u00a0 Many times, it happens because people are not always conscious about how they handle sensitive information.\u00a0 Employees are often the greatest threat in the compromise of sensitive information.<\/p>\n<p>Following the simple steps below will help assure your ship is not sunk by loose lips:<\/p>\n<p>1. Know your information.\u00a0 Is the information you handle sensitive or confidential?\u00a0 What would be the damage if it gets out to the public or one of our competitors?<\/p>\n<p>2. Label sensitive, proprietary or confidential information.\u00a0 You may know that the information is sensitive, but do your co-workers?\u00a0 This is solved by labeling the document or data source as confidential.<\/p>\n<p>3.Stop and think before doing anything with the information.\u00a0 You should be conscious on how you use the information and where you store it. Don\u2019t share it with someone who doesn\u2019t need to know.<\/p>\n<p>4. Protect sensitive, proprietary or confidential information.\u00a0 This is a separate article by itself. In general here are some things you can do:<\/p>\n<ul>\n<li>Place it in a secure location (not the public folder or even your laptop hard drive).<\/li>\n<li>Better yet, don\u2019t store a copy outside of a protected area.\u00a0 Your PCs hard drives are neither secure nor protected.\u00a0 If you don\u2019t need a copy of a document, then don\u2019t keep it on your computer.<\/li>\n<li>Don\u2019t send it to an outside email address unless absolutely necessary.<\/li>\n<li>Encrypt it (using a tool like Microsoft Bitlocker)<\/li>\n<li>Remove any extra copies of sensitive documents.\u00a0 Maintain originals in a secure location and get rid of all other copies.<\/li>\n<\/ul>\n<p>5. Ask for help.\u00a0 Work with your security department.\u00a0 If you are the security department, ask for help from others.<\/p>\n<p>6. Be on the lookout.\u00a0 Inform security if you find sensitive information that you shouldn\u2019t be able to see.\u00a0 It\u2019s not to get someone else in trouble, but to protect your company.\u00a0 Security should collaborate with the originator to ensure its proper protection.<\/p>\n<p>These may seem like simple ideas, but they are still overlooked. A little time in security now can save many headaches later.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Are you watching what you are telling your neighbors?\u00a0 Do you guard information in your care to make sure only those people with a need to know can see it? Hopefully, you\u2019re not accidentally letting any secrets slip.\u00a0 It could be disastrous if confidential information got out to your competitors.\u00a0 It could hurt your sales, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[32,18,3],"tags":[],"class_list":["post-221","post","type-post","status-publish","format-standard","hentry","category-concepts","category-online-safety-tips","category-security-management"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/posts\/221","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/comments?post=221"}],"version-history":[{"count":3,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/posts\/221\/revisions"}],"predecessor-version":[{"id":224,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/posts\/221\/revisions\/224"}],"wp:attachment":[{"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/media?parent=221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/categories?post=221"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurity.bellevue.edu\/index.php\/wp-json\/wp\/v2\/tags?post=221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}