Home > Articles > Operating Systems, Server > Microsoft Servers

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Analyzing Existing Systems and Applications

A good security design implements an effective security policy. The first step is to determine how effectively the current information systems accomplishes this. There are two goals here: understanding the policy and the rationale behind it, and understanding the current systems and applications.

So just what is "security policy?" Let's first discuss what it is not. Security policy is not a listing of Windows registry hacks, or the application of privileges, resource permissions, or membership in groups. It is most definitely not the blanket application of the latest Microsoft security bulletin "hot fix" or third-party program. Security policy is written direction from management on a wide range of security goals. Operating systems specific configuration, patching, and the use of security products and protocols can fulfill, or implement, these management directives. For example, security policy for the Lawrence Livermore Labs may state that secure areas exist from which no copy of information should be removed. The implementation of this policy may include the exclusion of Palm Pilot systems with wireless capabilities because they might be used to transmit data from computer systems within the secure area by broadcast from one Palm unit inside the area to another outside. While this is a good security implementation for Lawrence Livermore Labs, your organization may choose to have a less strict policy, and the banning of wireless Palm units may never be a part of its implementation. Let's use a Windows 2000-related scenario while considering the following security policy:

"Every computer system shall have a warning banner clearly visible to all who attempt to log on to the system. The banner will include the legal warning defined in paragraph B section II."

How would you implement this policy on Windows 2000 systems? On Windows NT systems? What is the most efficient way to do so?

Your assessment of the impact of this security policy and its place in your security design would be:

  • To determine which systems in the current environment already follow this policy and how it has been implemented.

  • To determine which systems do not follow this policy.

  • To attempt to determine the manner in which new systems and existing systems will follow this policy, and the impact of doing so. (Will it be difficult to implement? Will it require extraordinary efforts to implement it? Will the cost of implementation outweigh the benefits of implementation? What would the cost be if it were not implemented?)

Remember, your job as security architect is not to make the policy, but to design the implementation of the policy, to advise management on the relative ways in which this can be done, and to show the benefits and costs of the options. Ultimately, management will decide if a policy needs to be changed, or a new one added. This does not mean that you ignore your knowledge of specific threats to implemented systems. Management is looking to you to provide the information necessary for the development of new policies. Policies, however, by their nature are usually vaguely defined.

To assist management, your knowledge of the current systems and applications and the environment they exist in will help you in determining where security is good, where it can be improved, and where it is non-existent.

  • Applications: Are legacy applications being used on Windows NT that require extreme relaxation of file and registry security? Are versions of current applications available that meet strict Windows 2000 application requirements?

  • Systems: How many of the current workstations run Windows 9x? Windows NT? MS-DOS? Macintosh? Unix? How many of these systems are scheduled for upgrade or replacement immediately? Within six months? A year? What are the roles of servers? File servers? Email servers? Database servers? How are all these systems (workstations and servers) protected? How are they individually configured? Windows NT and/or 9x systems policies? Third-party products? In-house scripts and programs? How are hotfixes and service packs managed? What is the status of current systems? Is a process in place to determine the necessary security updates or configurations?

    If you do not have this information, detail the configuration of hardware and software inventories (bios, service packs, policies).

  • Network: What current connectivity exists? Are there interfaces with branch offices? Remote Access Servers for dial-up? Is Internet connectivity a right or privilege? Do you interface with NetWare? Unix? Mainframe hosts? How are these connections protected?

  • History: A good source for background on current systems, and the application of or lack of security consideration, is the records kept of past intrusions. Would better security design have prevented a successful attack? How was the information gained used in securing the systems after the fact? Was it successful? How can the implementation of Windows 2000 deal with these issues?

  • DNS: Determine the capabilities of current DNS servers. Do the servers allow dynamic registration? Can they handle service resource records? Windows 2000 implementations do not require the ability to do dynamic DNS registration, but they do require that DNS servers are capable of storing and using service resource records. BIND 4.97 and BIND 8.x support service resource records. Which DNS are you using? How can this service be secured?

Much of this information may be available as a result of studies carried out during network or Active Directory design and analysis. These topics are specifically presented in other Seattle Pacific University courses. If so, review it with an eye to security. While we are studying security design as a separate component, this is not the best plan in the real world. In fact, the hallmark of a good organization is its recognition of the need to incorporate security into every planning stage.

Your knowledge of planned upgrades and new implementations can be used to avoid costly mistakes, as well as allow you to work these systems into your overall design. For example, if you have no knowledge of the impending implementation of a Public Key Infrastructure using a third-party product, you might design an elaborate Windows 2000 PKI that may not integrate with the third-party PKI; you also might implement other security products or policies that will not be necessary after the third-party PKI is in place. If you are aware of this impending development, you may be able to steer development in ways that will ensure the integration of the third-party PKI with Windows 2000. At the least, you can incorporate this knowledge into your design. The questions to ask should center on helping you gain a knowledge of the third-party PKI, and the reasons for its implementation. Your attitude should ensure cooperation and the free flow of information. You cannot afford to be offensive (calling others "stupid" for not using the free PKI in Windows 2000 will not get you invited to important planning meetings), nor can you afford to be defensive (answering questions on Windows 2000 PKI with half-baked opinions you read in the press, presenting it as inferior but "hey, it's free," etc. will do nothing toward instilling confidence in your Windows 2000 design).

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020