<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>a good security policy by maizatul akmar</title>
      <link>https://padlet.com/maizatul82/agoodsecuritypolicy</link>
      <description>explain by referring your company</description>
      <language>en-us</language>
      <pubDate>2017-04-10 11:09:06 UTC</pubDate>
      <lastBuildDate>2017-04-11 09:49:03 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>The Five Infea</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165815521</link>
         <description><![CDATA[<div>A security policy is a written statement describing which assets to protect and why they are being protected,who is responsible for that protection,and which behavior are acceptable and which are not.The policy primarily addresses physical security,network security,access authorization,virus protection and disaster recovery.The policy develops over time and is a living document that the company management and security personnel must review and update at regular intervals.A GOOD POLICY should address the following :<br>1)<strong>Authentication</strong>:who is trying to access the site?<br>2)<strong>Access Control</strong>:who is allowed to log on to and access the site?<br>3)<strong>Secrecy</strong>:who is permitted to view selected information?<br>4)<strong>Data integrity</strong>:who is allowed to change data?<br>5)<strong>Audit:</strong>who or what causes specific events to occur,and when?&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 05:51:31 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165815521</guid>
      </item>
      <item>
         <title>Nash Group</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165819713</link>
         <description><![CDATA[<div>A good security policy, The first step in any project to prepare a security policy document is to determine what elements to include in your policy. Be sure to consider all the key elements your IT staff manages.<br>1) Security accountability: Stipulate the security roles and responsibilities of general users</div><div>2) Security training: Define a security training plan for key staff who manage day-to-day security operations in order to sustain your security policy and keep your security staff current with the latest techniques.</div><div>3System policies: Define the host security configuration for all mission-critical operating systems and servers.<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 06:36:22 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165819713</guid>
      </item>
      <item>
         <title>BIG APPLE</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165820191</link>
         <description><![CDATA[<div>&nbsp;A good security policy is compromised of several factors. The most important factor is that it must be usable. A security policy is of no use to an organization or the individuals within an organization if they cannot implement the guidelines or regulations within the policy. It should be concise, clearly written and as detailed as possible in order to provide the information necessary to implement the regulation. It should be versioned and dated in order to easily identify the most current document, and should be structured internally in such a way that pertinent or required information is identified and located easily within the document for reference. A good security policy also takes into account the existing or implicit rules in use. Business processes involve over time within organizations as personnel learn more efficient ways of processing information. A security policy should in no way impede or interfere with the business. Rather, it should enhance the process, providing confidence in the security of the day to day operations. It must be enforceable with security tools where appropriate, and with sanctions where actual prevention is not technically feasible. Firewalls, intrusion detection&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 06:41:40 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165820191</guid>
      </item>
      <item>
         <title>Bella Ammara </title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165831015</link>
         <description><![CDATA[<div>Nestle<br><strong>Referrals&nbsp;</strong></div><div>If you send a business contact or acquaintance an e-mail or a downloadable application from the web site referring the acquaintance to this web site, the "referral" information you provide is used on a one-time basis to facilitate this communication and is not further retained by Nestlé.</div><div><strong>Cookie / Tracking Technology&nbsp;</strong></div><div>The web site may use cookie and tracking technology depending on the features offered. Cookie and tracking technology are useful for gathering information such as browser type and operating system, tracking the number of visitors to the web site, and understanding how visitors use the web site. Further, cookies can also help customize the web site for visitors and offer an efficient manner to log into the sign-in sections of the web site. Personal information cannot be collected via cookies and other tracking technology. However, if you previously provided personally identifiable information, cookies may be tied to such information. Aggregate cookie and tracking information may be shared with third parties.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 08:20:57 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165831015</guid>
      </item>
      <item>
         <title>ASTRO GROUP</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165831953</link>
         <description><![CDATA[<div>A good security policies will show that most security breaches are preventable. To prevent these breaches, companies need to develop and enforce solid security policy plans.<br><br></div><div><strong>Wireless Security Access Policy</strong></div><div>End-users are increasingly using inexpensive wireless networking resources to connect themselves to the corporate network. Because wireless network segments are inherently less secure than conventionally wired components, wholesale, uncontrolled use of wireless access will expose the organization to additional risk. Craft and implement a wireless security access policy for your organization to mitigate risk.<br><br></div><div><strong>Software Installation Policy</strong></div><div>The goal of a Software Installation Policy is to identify permitted standard software titles, clearly communicate what is prohibited, and outline proper procedures for installation. Use this template to craft a policy suited to the needs of your enterprise.<br><br></div><div><strong>Mobile Device Acceptable Use Policy</strong></div><div>The policy applies to any hardware and related software that could be used to access corporate resources, even if said equipment is not corporately sanctioned, owned or supplied.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 08:28:00 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165831953</guid>
      </item>
      <item>
         <title>Group 8</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165832946</link>
         <description><![CDATA[<div>A good security policy shoul address tge following:<br>1. Authentication: who is trying to access the site?<br>2. Access control: who is allowed to log on to and access the site?&nbsp;<br>3. Secrecy: who is permitted to view selected information?<br>4. Data integrity: who is allowed to change data?<br>5. Audit: who or what causes specific events to occur, and when?<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 08:36:18 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165832946</guid>
      </item>
      <item>
         <title>Al- Ikhsan Group</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165836579</link>
         <description><![CDATA[<div> A good security policy is compromised of several factors. The most important factor is that it must be usable. A security policy is of no use to an organization or the individuals within an organization if they cannot implement the guidelines or regulations within the policy. It should be concise, clearly written and as detailed as possible in order to provide the information necessary to implement the regulation. It should be versioned and dated in order to easily identify the most current document, and should be structured internally in such a way that pertinent or required information is identified and located easily within the document for reference. A good security policy also takes into account the existing or implicit rules in use. Business processes evolve over time within organizations as personnel learn more efficient ways of processing information. A security policy should in no way impede or interfere with the business. Rather, it should enhance the process, providing confidence in the security of the day – to – day operations. It must be enforceable with security tools where appropriate, and with sanctions where actual prevention is not technically feasible. Firewalls, intrusion detection  systems, anti-virus applications are some of the tools that can be used to apply the policies in the business environment. However, manual processes should be laid out within the policy, as not every security policy is enforceable via an automated system or application. One of the most common misconceptions is that security policies are driven only by security systems. In actuality, it is the processes outlined within the security policy, and the people who carry out the required policies that create a secure environment. </div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 09:09:48 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165836579</guid>
      </item>
      <item>
         <title>Company nike</title>
         <author>misshondaathirah</author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165839035</link>
         <description><![CDATA[<div>Geng Group NUR ATHIRAH<br><br>GIVE US INFORMATION<br><br>We collect information you give us or permit us to access. Information may include, but is not limited to, your name, image, birth date, email and physical address, telephone number, gender, contact lists, social media information and profile, location (GPS) information, activity and performance information, and when necessary, credit card information.<br><br><br>WE COLLECT FROM YOUR INFORMATION<br>We may automatically collect information regarding your interaction with, and use of, our products and services. Information we may collect includes, but is not limited to, your telephone number, Device identifier and hardware information, IP address, browser type and language, cookie information, system type, whether you have enabling software to access certain features, access times, referring website URLs, information about your purchases and other information about your interactions with us.<br><br><br></div><div>WE COLLECT FROM OTHER NIKE INTERACTIONS AND THIRD PARTIES<br>We may combine information you give us with other information from NIKE sources, transactions and communications. This may include, but is not limited to, information from NIKE stores, direct mail, catalogs, events, products and applications, or other NIKE interactions. We may also combine that information with data that is publicly available and data from third parties. We also collect information about gift recipients provided by the giver.<br><br>CHILDREN'S PRIVACY<br>We do not knowingly collect or solicit personal information from children under 13.<br><br></div><div><br><br></div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 09:32:52 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165839035</guid>
      </item>
      <item>
         <title>group 7</title>
         <author></author>
         <link>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165840865</link>
         <description><![CDATA[<div>All security policies should include a well-defined security vision for the organization.&nbsp; The security vision should be clear and concise and convey to readers the intent of the policy.&nbsp; Also included in this section should be details of what if any security standards your organization is following.&nbsp; Examples of which are ISO 27001 Information Security Management System (sometimes still referred to as<strong> </strong>ISO 17799),<strong> </strong>NIST Standard (National Institute of Standards and Technology) or any of the other standards available to you.<br><br><br><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-04-11 09:47:00 UTC</pubDate>
         <guid>https://padlet.com/maizatul82/agoodsecuritypolicy/wish/165840865</guid>
      </item>
   </channel>
</rss>
