NET Frameworks

The Microsoft .NET Framework is a software framework available with several Microsoft Windows operating systems. It includes a large library of coded solutions to prevent common programming problems and a virtual machine that manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform.

The framework's Base Class Library provides a large range of features including user interface, data and data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications.

Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together compose the .NET Framework.

ASP - Active Server Pages

Active Server Pages (ASP), also known as Classic ASP, was Microsoft's first server-side script engine for dynamically-generated web pages. Initially released as an add-on to Internet Information Services (IIS) via the Windows NT 4.0 Option Pack, it was subsequently included as a free component of Windows Server (since the initial release of Windows 2000 Server).

Developing rich functionality in ASP websites is enabled by the active scripting engine's support of the Component Object Model (COM), with each object providing a related group of frequently-used functions and data attributes. In ASP 2.0 there were six built-in objects: Application, ASPError, Request, Response, Server, and Session. Session, for example, is a cookie-based session object that maintains the state of variables from page to page. Functionality is further extended by objects which, when instantiated, provide access to the environment of the web server; as an example FileSystemObject (FSO) is used to create, read, update and delete files.

Web pages with the .asp file extension use ASP, although some Web sites disguise their choice of scripting language for security purposes (e.g. still using the more common .htm or .html extension). Pages with the .aspx extension are ASP.NET (based on Microsoft's .NET Framework) and compiled, which makes them faster and more robust than the than server-side scripting in ASP which is interpreted at run-time; however, many ASP.NET pages still include some ASP scripting. Such marked differences between ASP and ASP.NET have lead to the term Classic ASP being used, which also implies some nostalgia for the simpler platform.

Most ASP pages are written in VBScript, but any other Active Scripting engine can be selected instead by using the @Language directive or the <script language="language" runat="server"> syntax. JScript (Microsoft's implementation of ECMAScript) is the other language that is usually available. PerlScript (a derivative of Perl) and others are available as third-party installable Active Scripting engines.

Access

Microsoft Office Access, previously known as Microsoft Access, is a relational database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software development tools. It is a member of the Microsoft Office suite of applications and is included in the Professional and higher versions for Windows and also sold separately. There is no version for MacOS or for Microsoft Office Mobile.

Access stores data in its own format based on the Access Jet Database Engine. It can also import or link directly to data stored in other Access databases, Excel, SharePoint lists, text, XML, Outlook, HTML, dBase, Paradox, Lotus 1-2-3, or any ODBC-compliant data container including Microsoft SQL Server, Oracle, MySQL and PostgreSQL. Software developers and data architects can use it to develop application software and non-programmer "power users" can use it to build simple applications. It supports some object-oriented techniques but falls short of being a fully object-oriented development tool

Access Privileges

It is also define as the actions that can be performed on a provider and the components owned by it. By default, you are granted the highest level of access, Manage access privilege, on any provider you create. With Manage privileges, not only can you perform actions on the provider and create components within it, but you can grant access privileges to other Portal developers. You can also delete the provider.

Access Privileges

Access privileges determine which portal objects a user can browse or edit, which objects appear in search results, and which can be added to My Pages and community pages.

Access to each object and document in the portal is controlled through the following access privileges:

Note:

·         The Everyone group (all users) has mandatory Read access to authentication sources, content types, filters, invitations, and properties.

·         If a user is a member of more than one group included in the list, or if they are included as an individual user and as part of a group, that user gets the highest privilege available to the user for the object. For example, if a user is part of the Everyone group (which has Read access) and the Administrators group (which has Admin access), that user gets the higher privilege to the object: Admin.

·         Access privileges are based on the security of the folder in which the object is stored. Changes to the security of a folder apply to all the objects within that folder. For example, if a document in the folder is shared with another folder (such as when a document is copied from one folder to another), the security of the document is changed in both locations.

·          

Administrator (as an IT resource)

Welcome to User Management Resource Administrator (UMRA). User Management Resource Administrator (UMRA) is a comprehensive User Account Management solution that can help you to control and manage Active Directory. While extremely powerful and flexible, Active Directory can be a complex environment to manage. UMRA is an enterprise solution focused on Active Directory user account management and it provides a central point of control to manage, control and report on Active Directory user accounts. Besides Active Directory, UMRA also manages all user account resources like home- and profile directories, Exchange mailboxes, Terminal Services settings, group memberships and NTFS permissions.

UMRA supports a wide variety of functions and a number of different interfaces. Features include the creation, deletion and configuration of user accounts, mailboxes, (home) directories, groups, group memberships, permission settings and many more.

With the different UMRA interfaces, you can create and manage user accounts in bulk, one-by-one, in a delegated manner, by a command-line interface and through a web interface.

UMRA Scripts

UMRA uses scripts to perform its tasks. A script is a collection of statements or actions (examples: Create user, Setup mailbox) that each perform a specifc task. The different actions available in UMRA to compose a script, focus on the management of user accounts, resources, mailboxes and so on. A script with multiple actions for instance create a user account, sets up the home and profile directories and permissions, adds the new user account to a number of groups and creates an Exchange mailbox for the user account.

UMRA supports a graphical interface to setup a new script or edit existing scripts. The interface is designed to make it very easy to setup a new script or edit an existing script.

UMRA Projects

Different types of UMRA projects exist. Each project contains an UMRA script and a specification how the script is executed. The two main project types are:

1.      Mass create-update-delete projects: The project contains a table with input data. The input data is for instance read from a csv file. For each line of the input file, the script is executed. A mass project is typically used to create, update or delete user accounts and resources. See Principle of operation for more information.

2.      Form project: The project contains the definition of a form. The form typically contains a number of fields like tables, text, input fields. The form is presented in a separate interface (UMRA forms) or a web-interface (browser). When the form fields are specified by the end-user and the form is submitted, the script of the form project is executed. See Form project - Principle of operation for more information.

UMRA Software

UMRA consists of a number of software applications:

1.      UMRA Console: The main application that is primarily used to manage all UMRA projects and manage the UMRA service. To use UMRA, you always start with the UMRA Console application.

2.      UMRA Service: The UMRA service is used to execute delegated tasks. The UMRA Service is accessed through the UMRA Console, UMRA Forms and UMRA Automation software. You only need to install the UMRA Service application if you want to execute forms projects. See UMRA Delegation - General or more information.

3.      UMRA Forms: The Windows interface to show and submit delegated forms. The UMRA Forms application is most often used by helpdesk employees. The UMRA Forms application interfaces with the UMRA Service application directly. See UMRA forms - Introduction for more information.

4.      UMRA Automation: UMRA can be integrated with other employee management systems to automate Active Directory user account management tasks. For instance: When an employee leaves an organization and is excluded from an employee information system, Active Directory needs to be updated, by disabling or removal of the associated user account and network resources. With UMRA, the UMRA service can execute these tasks automatically when the employee information system is updated. See UMRA Automation - Introduction for more information.

Authentication

For other uses of the terms "authentication", "authentic" and "authenticity", see authenticity.

Authentication (from Greek: αυθεντικός; real or genuine, from authentes; author) is the act of establishing or confirming something (or someone) as authentic, that is, that claims made by or about the subject are true. This might involve confirming the identity of a person, the origins of an artifact, or assuring that a computer program is a trusted one.

Authentication methods

In art, antiques, and anthropology, a common problem is verifying that a given artifact was produced by a certain famous person, or was produced in a certain place or period of history.

There are two types of techniques for doing this.

The first is comparing the attributes of the object itself to what is known about objects of that origin. For example, an art expert might look for similarities in the style of painting, check the location and form of a signature, or compare the object to an old photograph. An archaeologist might use carbon dating to verify the age of an artifact, do a chemical analysis of the materials used, or compare the style of construction or decoration to other artifacts of similar origin. The physics of sound and light, and comparison with a known physical environment, can be used to examine the authenticity of audio recordings, photographs, or videos.

Attribute comparison may be vulnerable to forgery. In general, it relies on the fact that creating a forgery indistinguishable from a genuine artifact requires expert knowledge, that mistakes are easily made, or that the amount of effort required to do so is considerably greater than the amount of money that can be gained by selling the forgery.

Criminal and civil penalties for fraud, forgery, and counterfeiting can reduce the incentive for falsification, depending on the risk of getting caught.

The second type relies on documentation or other external affirmations. For example, the rules of evidence in criminal courts often require establishing the chain of custody of evidence presented. This can be accomplished through a written evidence log, or by testimony from the police detectives and forensics staff that handled it. Some antiques are accompanied by certificates attesting to their authenticity. External records have their own problems of forgery and perjury, and are also vulnerable to being separated from the artifact and lost.

Currency and other financial instruments commonly use the first type of authentication method. Bills, coins, and cheques incorporate hard-to-duplicate physical features, such as fine printing or engraving, distinctive feel, watermarks, and holographic imagery, which are easy for receivers to verify.

Consumer goods such as pharmaceuticals, perfume, fashion clothing can use either type of authentication method to prevent counterfeit goods from taking advantage of a popular brand's reputation (damaging the brand owner's sales and reputation). A trademark is a legally protected marking or other identifying feature which aids consumers in the identification of genuine brand-name goods.

Database administrator

A database administrator (DBA) is a person who is responsible for the environmental aspects of a database. The role of a database administrator has changed according to the technology of database management systems (DBMSs) as well as the needs of the owners of the databases. For example, although logical and physical database design are traditionally the duties of a database analyst or database designer, a DBA may be tasked to perform those duties.

 Duties

The duties of a database administrator vary and depend on the job description, corporate and Information Technology (IT) policies and the technical features and capabilities of the DBMS being administered. They nearly always include disaster recovery (backups and testing of backups), performance analysis and tuning, data dictionary maintenance, and some database design.

Some of the roles of the DBA may include

• Installation of new software — It is primarily the job of the DBA to install new versions of DBMS software, application software, and other software related to DBMS administration. It is important that the DBA or other IS staff members test this new software before it is moved into a production environment.

• Configuration of hardware and software with the system administrator — In many cases the system software can only be accessed by the system administrator. In this case, the DBA must work closely with the system administrator to perform software installations, and to configure hardware and software so that it functions optimally with the DBMS.

• Security administration — One of the main duties of the DBA is to monitor and administer DBMS security. This involves adding and removing users, administering quotas, auditing, and checking for security problems.

• Data analysis — The DBA will frequently be called on to analyze the data stored in the database and to make recommendations relating to performance and efficiency of that data storage. This might relate to the more effective use of indexes, enabling "Parallel Query" execution, or other DBMS specific features.

• Database design (preliminary) — The DBA is often involved at the preliminary database-design stages. Through the involvement of the DBA, many problems that might occur can be eliminated. The DBA knows the DBMS and system, can point out potential problems, and can help the development team with special performance considerations.

• Data modeling and optimization — By modeling the data, it is possible to optimize the system layouts to take the most advantage of the I/O subsystem.

• Responsible for the administration of existing enterprise databases and the analysis, design, and creation of new databases.
• Data modeling, database optimization, understanding and implementation of schemas, and the ability to interpret and write complex SQL queries
• Proactively monitor systems for optimum performance and capacity constraints
• Establish standards and best practices for SQL
• Interact with and coach developers in Structured Query Language (SQL) scripting

Electronic commerce, commonly known as e-commerce or eCommerce, consists of the buying and selling of products or services over electronic systems such as the Internet and other computer networks. The amount of trade conducted electronically has grown extraordinarily with wide-spread Internet usage. A wide variety of commerce is conducted in this way, spurring and drawing on innovations in electronic funds transfer, supply chain management, Internet marketing, online transaction processing, electronic data interchange (EDI), inventory management systems, and automated data collection systems. Modern electronic commerce typically uses the World Wide Web at least at some point in the transaction's lifecycle, although it can encompass a wider range of technologies such as e-mail as well.

A large percentage of electronic commerce is conducted entirely electronically for virtual items such as access to premium content on a website, but most electronic commerce involves the transportation of physical items in some way. Online retailers are sometimes known as e-tailers and online retail is sometimes known as e-tail. Almost all big retailers have electronic commerce presence on the World Wide Web.

Electronic commerce that is conducted between businesses is referred to as business-to-business or B2B. B2B can be open to all interested parties (e.g. commodity exchange) or limited to specific, pre-qualified participants (private electronic market). Electronic commerce that is conducted between businesses and consumers, on the other hand, is referred to as business-to-consumer or B2C. This is the type of electronic commerce conducted by companies such as Amazon.com.

Electronic commerce is generally considered to be the sales aspect of e-business. It also consists of the exchange of data to facilitate the financing and payment aspects of the business transactions.

Encryption

In cryptography, encryption is the process of transforming information (referred to as plaintext) using an algorithm (called cipher) to make it unreadable to anyone except those possessing special knowledge, usually referred to as a key. The result of the process is encrypted information (in cryptography, referred to as cipher text). In many contexts, the word encryption also implicitly refers to the reverse process, decryption (e.g. “software for encryption” can typically also perform decryption), to make the encrypted information readable again (i.e. to make it unencrypted).

Encryption has long been used by militaries and governments to facilitate secret communication. Encryption is now used in protecting information within many kinds of civilian systems, such as computers, storage devices (e.g. USB flash drives), networks (e.g. the Internet, e-commerce), mobile telephones, wireless microphones, wireless intercom systems, Bluetooth devices and bank automatic teller machines. Encryption is also used in digital rights management to prevent unauthorized use or reproduction of copyrighted material and in software also to protect against reverse engineering (see also copy protection).

Encryption, by itself, can protect the confidentiality of messages, but other techniques are still needed to protect the integrity and authenticity of a message; for example, verification of a message authentication codes (MAC) or a digital signature. Standards and cryptographic software and hardware to perform encryption are widely available, but successfully using encryption to ensure security may be a challenging problem. A single slip-up in system design or execution can allow successful attacks. Sometimes an adversary can obtain unencrypted information without directly undoing the encryption. See, e.g., traffic analysis, TEMPEST, or Trojan horse.

One of the earliest public key encryption applications was called Pretty Good Privacy (PGP), according to Paul Rubens. It was written in 1991 by Phil Zimmermann and was bought by Network Associates in 1997 and is now called PGP Corporation.

There are a number of reasons why an encryption product may not be suitable in all cases. First e-mail must be digitally signed at the point it was created to provide non-repudiation for some legal purposes, otherwise the sender could argue that it was tampered with after it left their computer but before it was encrypted at a gateway according to Paul. An encryption product may also not be practical when mobile users need to send e-mail from outside the corporate network.*

for an automotive related industry, is supposed to have created the term to modernize the outdated phrase "data processing". The Oxford English Dictionary, however, in defining information technology as "the branch of technology concerned with the dissemination, processing, and storage of information, esp. by means of computers" provides an illustrative quote from the year 1958 (Leavitt & Whisler in Harvard Business Rev. XXXVI. 41/1 "The new technology does not yet have a single established name. We shall call it information technology.") that predates the so-far unsubstantiated Domsic coinage.

Intellectual property

Intellectual property (IP) is legal property rights over creations of the mind, both artistic and commercial, and the corresponding fields of law. Under intellectual property law, owners are granted certain exclusive rights to a variety of intangible assets, such as musical, literary, and artistic works; ideas, discoveries and inventions; and words, phrases, symbols, and designs. Common types of intellectual property include copyrights, trademarks, patents, industrial design rights and trade secrets.

The majority of intellectual property rights provide creators of original works economic incentive to develop and share ideas through a form of temporary monopoly. While credited with significant contributions to modern economic growth, some have criticised the expansion in nature and scope of IP laws.

Although many of the legal principles governing intellectual property have evolved over centuries, it was not until the late 20th century that the term intellectual property began to be used as a unifying concept

ISO

An ISO image is an archive file (also known as a disk image) of an optical disc in a format defined by the International Organization for Standardization (ISO). This format is supported by many software vendors. ISO image files typically have a file extension of .ISO but Mac OS X ISO images often have the extension .CDR. The name ISO is taken from the ISO 9660 file system used with CD-ROM media, but an ISO image can also contain UDF file system because UDF is backward-compatible with ISO 9660.

Malicious Code

Malicious code (also called vandals) is a new breed of Internet threat that cannot be efficiently controlled by conventional antivirus software alone. In contrast to viruses that require a user to execute a program in order to cause damage, vandals are auto-executable applications.

Patch

Patch is a Unix program that updates text files according to instructions contained in a separate file, called a patch file. The patch file (also called a patch for short) is a text file that consists of a list of differences and is produced by running the related diff program with the original and updated file as arguments. Updating files with patch is often referred to as applying the patch or simply patching the files.

Purge

Purge is the removal of people who are considered undesirable by those in power from a government, from another organisation, or from society as a whole. Purges can be peaceful or violent; many will end with the imprisonment or exile of those purged, but in some cases they will simply be removed from office. Restoring people who have been purged is known as rehabilitation

Spoofing

spoofing attack is a situation in which one person or program successfully masquerades as another by falsifying data and thereby gaining an illegitimate advantage.

User identifier (Unix)

On Unix-like operating systems, users are identified within the kernel by an unsigned integer value called a user identifier, often abbreviated to UID or User ID. The range of its values varies amongst different systems; at the very least, a UID is a 15-bit integer, ranging between 0 and 32767, with the following restrictions:

• The superuser must always have a UID of zero (0).
• The user "nobody" was traditionally assigned the largest possible UID (as the opposite of the Superuser), 32767. More recently, the user is assigned a UID in the system range (1–100, see below) or between 65530–65535.
• UIDs from 1 to 100 are otherwise reserved for system use by convention; some manuals recommend that UIDs from 101 to 499 (RedHat) or even 999 (Debian) be reserved as well.

The UID value references users in the /etc/passed file. Shadow password files and Network Information Service also refer to numeric UIDs. The user identifier is a necessary component of Unix file systems and processes. Some operating systems might have support for 16-bit UIDs, making 65536 unique IDs possible, though a modern system with 32-bit UIDs will potentially make 4,294,967,296 (2³²) distinct values available.