G3+-+Subpage+4+-+Control+and+Solutions+of+Social+and+Ethical+Issues

 Hey, I added some more possible solutions that i found on the web.

Hey guys, great work so far. For the three main comm. systems, I found these great articles and pages about solutions: Cellphones: http://www.news.com/Cell-phones-to-get-virus-protection/2100-7355_3-5608794.html http://hardware.slashdot.org/article.pl?sid=05/09/02/2025205

Email: http://us.mcafee.com/virusInfo/default.asp?id=tips&http://www.mcafee.com/anti-virus/virus_tips.asp http://en.wikipedia.org/wiki/List_of_antivirus_software http://support.microsoft.com/kb/49500 http://www.itsecurity.com/features/25-common-email-security-mistakes-022807/

There are cryptography applications that can serve as a remedy the issues of privacy and anonymity. For example, Virtual Private Networks or the Tor anonymity network can be used to encrypt traffic from the user machine to a safer network while GPG, PGP or S/MIME can be used for end-to-end message encryption, and SMTP STARTTLS or SMTP over Transport Layer Security/Secure Sockets Layer can be used to encrypt communications for a single mail hop between the SMTP client and the SMTP server. Additionally, many mail user agents do not protect logins and passwords, making them easy to intercept by an attacker. Encrypted authentication schemes such as SASL prevent this.
 * Email and Privacy:**

"When it comes to archiving, organisations should take a two-pronged approach, to reduce the risk and retain corporate knowledge. Firstly, users should be frequently educated about email retention policies. In addition, an archiving solution should enable administrators to remove items from users’ mailboxes based on administrator-configured options such as the age or size of a message. Administrators should be able to control, retain and backup the email files, by consolidating the information stored in email files whilst ensuring that users are prevented from simply creating new emails.
 * Email and Security:**

Organisations must plan for the inevitable request to recover data from backups and archives. For the most critical users, such as company executives, many administrators have turned to slow, expensive brick-level backups to provide quick restoration of data to a select few. However, with the onslaught of regulations dictating email retention policies, organisations need to have a comprehensive recovery plan for their entire organisation. For example, Bank of America was fined $10 million USD in March 2004 when it failed to turn over messaging data to the U.S. Security and Exchange Commission (SEC) in a timely manner (currently interpreted as only 36 to 72 hours). Faced with this challenge, the traditional method of restoring lorry loads of backup tapes to find all the communications that fit specific criteria is extremely time consuming, and not entirely accurate. An email recovery solution must allow for individual, message-level items, including; messages, appointments, tasks, contacts, and attachments to be quickly restored from regular backups and information stores without setting up a dedicated recovery server.

A large risk to email data within the enterprise is unlawful access to highly sensitive mailbox information. Without a method to both secure and audit this access, there can be no guarantee that data is in fact secured. This can be any link in a lengthy chain, all the way from the administrator resetting, and therefore knowing, the CEO’s password through to proving that some other party had access to his/her mail account. Authentication and mailbox data security are both constant battles that need to be monitored closely to ensure that the critical data contained within the email system is available only to those for whom it’s intended."

Intranets: http://anonymouse.org/cgi-bin/anon-www.cgi/http://intranetblog.blogware.com/blog/_archives/2007/2/13/2734653.html http://jobfunctions.bnet.com/whitepaper.aspx?docid=261981 http://www.ssimail.com/Sesfacts.htm

1208441716


 * = DISADVANTAGES OF INTRANETS ||= SOLUTIONS TO DISADVANTAGES ||= LIMITATIONS OF SOLUTIONS ||
 * < 
 * Management concerns** ||
 * < possible loss of control ||< monitoring of activities - logs ||  ||
 * < hidden/unknown complexity of costs ||< monitoring transactions/maintenance ||  ||
 * < potential for chaos ||< control of information by facilitating transactions ||  ||
 * Security concerns** ||  ||
 * < unauthorized access ||< passwords, encryption ||  ||
 * < abuse of access ||< close monitoring, loggers ||  ||
 * < packet sniffing ||< encryption of passwords and other info ||  ||
 * Productivity concerns** ||  ||
 * < overabundance of information ||< maintenance of pages and information in intranet ||  ||
 * < information overload lowering productivity ||< weeding out irrelevant/outdated information/upgrades ||  ||
 * < users set up own web pages ||< facilitation, password system ||  ||
 * < information overload lowering productivity ||< weeding out irrelevant/outdated information/upgrades ||  ||
 * < users set up own web pages ||< facilitation, password system ||  ||

**Strategies to control the use of intranets (MANAGEMENT)** The planning and implementation of the intranets is one of the most important steps for facilitating communication and transactions within a corporation. These are some factors to consider when creating and managing intranets:  > 1208395334
 * What they hope to achieve from the intranet
 * Which person or department would "own" (take control of) the technology and the implementation
 * How and when existing systems would be phased out/replaced
 * How they intend to make the intranet secure
 * How they'll ensure to keep it within legislative and other constraints
 * <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Level of interactivity desired <span style="COLOR: rgb(29,29,78)"> (wikis, online forms) <span style="COLOR: rgb(29,29,78)">.
 * <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Is the input of new data and updating of existing data to be centrally controlled or devolved.
 * Steps to ensure the implementation of an intranet runs smoothly:**
 * 1) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">User involvement to identify users' information needs.
 * 2) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Setting up a web server with the correct hardware and software.
 * 3) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Setting up web server access using a TCP/IP network.
 * 4) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Installing the user programs on all required computers.
 * 5) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">Creating a homepage for the content to be hosted
 * 1) <span style="COLOR: rgb(10,22,123)"><span style="COLOR: rgb(29,29,78)">User involvement in testing and promoting use of intranet.

The implication of software or technology aimed at aiding security in relation to mobile devices and Wireless communications and management in general:

- Mobile Security technology such as Mobile F-Secure, for example - The Encryption of data - Username / Password Interfaces - The use of solely Private Networks (such as Intranets)

1208264801

I suppose here we should also evaluate<span style="COLOR: rgb(0,0,0)"> the ways in which trans nat corps attempt to rectify some of the social/ethical issues.

For starters, I know that some organizations choose not to use some forms of technology, specifically as a result of these issues (e.g. Wi-Fi in many military installations). What about trans nat corps?

More to come.

1207815974