Glossary of Terms

Skip to Main Content

Apply

Common Searches

Login

Glossary

Filter:

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z All

R

R&D

RAC

RACE

Radar Intelligence

Radiated Signal

RADINT

Radio

Radio Fingerprinting

RADIUS (Remote Authentication Dial-In User Service) Server

RAM

Ramp

Random

Random Access Memory

RAS (remote access server)

RAT

Rating

Rating Maintenance Phase

Rating Maintenance Plan (RM-Plan, RM Plan)

Rating Maintenance Report (RMR)

Ratings Maintenance Phase (ramp)

Ratings Maintenance Plan

Rave

Rc File

RC4

RCCI

RD

Read

Read Up

Read/write Opening

Read/write Slot

Reading

Read-Only Memory

Read-Only Storage

Real

Real Operating System

Real Programmer

Realization Cost

Realm

Real-time backup

Real-Time Reaction

Reaper

Reasonability Checks

Re-authentication

Recertification

RechRef

Recommended practices

Record

Record Communication

Record Information

Recording Density

Recoverable Zone

Recovery Procedure

Recovery Procedures

Rectangle Slinger

Recursive Acronym

RED

RED Designation

RED Equipment Area

Red Key

RED Signal Line

RED/BLACK Concept

Redundancy Check

Reference Model of Open Systems Interconnection (OSI)

Reference Monitor

Reference Monitor Concept

Reference Monitors

Reference Validation

Reference Validation Mechanism

Refresh

Regexp

Register Dancing

Registered port numbers

Regrade

Reincarnation, Cycle Of

Reinvent The Wheel

REL

Reliability Testing

Religion Of CHI

Religious Issues

Remote Access Data Processing

Remote access server (RAS)

Remote access VPNs

Remote administration Trojans (RATs)

Remote Authentication Dial-In User Service (RADIUS) Server

Remote Batch Entry

Remote Batch Processing

Remote Call Forwarding

Remote Control Equipment

Remote Job Entry

Remote Rekeying

Remote Terminal Area

Remote Terminal Protection Devices

Remotely Accessed Resource-Sharing Computer System

Removable Disk Media

Removable Storage Media

Repair

Repertory Dialer

Replacement Cost

Report

Represented Asset Value

Reproducibility

Request

Request Data Transfer

Request for comment (RFC)

Requirements Traceability

Resale Parameter

Rescind

Reserve Keying Material

Resident Memory

Residue

Resource Encapsulation

Resource Sharing

Resource-Sharing Computer System

Response message

Responsibilities

Restart

Restore

Restricted Access

Restricted Area

Restricted Data

Restricted Service

Retcon

RETI

Retinal scanning

Retrieval Function

Retrieval Service

Return From The Dead

Return on investment (ROI)

Reusable password

Revenue

Review And Approval

RF

RFC

RFC (request for comment)

RFC [AuQ5][AuQ5]822

RFE

RFP

Risk

Risk acceptance

Risk Acceptance Process

Risk And Magnitude Of The Harm

Risk Assessment

Risk Management

Risk transference

RKV

RL

Rlogin

RM Plan

RM-Plan

RMR

RO

Roach

Robot

Robust

Rococo

Rogue

ROI (Return on investment)

Role-Based Access Controls

Roles

Roles And Responsibilities

ROM

Root

Rootkit

Rot13

Rotary Debugger

Rotation of duties

Route

Routine

Routing Control

Roving wiretaps

RPM

RQT

RSA

Rsh

RSN

RTBM

RTFAQ

RTFB

RTFM

RTFS

RTI

RTM

RTS

Rude

Rule

Rule Of Least Privilege

Rule-Based Access Controls

Rule-Based Security Policy

Rules-Based Access Controls

Run

RunAs

Runes

Runic

Run-Length Encoding

RWX

Pascal

n. An Algol-descended language designed by Niklaus Wirth on the CDC 6600 around 1967--68 as an instructional tool for elementary programming. This language, designed primarily to keep students from shooting themselves in the foot and thus extremely restrictive from a general-purpose-programming point of view, was later promoted as a general-purpose tool and, in fact, became the ancestor of a large family of languages including Modula-2 and Ada (see also bondage-and-discipline language). The hackish point of view on Pascal was probably best summed up by a devastating (and, in its deadpan way, screamingly funny) 1981 paper by Brian Kernighan (of K&R fame) entitled "Why Pascal is Not My Favorite Programming Language", which was turned down by the technical journals but circulated widely via photocopies. It was eventually published in "Comparing and Assessing Programming Languages", edited by Alan Feuer and Narain Gehani (Prentice-Hall, 1984). Part of his discussion is worth repeating here, because its criticisms are still apposite to Pascal itself after ten years of improvement and could also stand as an indictment of many other bondage-and-discipline languages. At the end of a summary of the case against Pascal, Kernighan wrote 9. There is no escape This last point is perhaps the most important. The language is inadequate but circumscribed, because there is no way to escape its limitations. There are no casts to disable the type-checking when necessary. There is no way to replace the defective run-time environment with a sensible one, unless one controls the compiler that defines the "standard procedures". The language is closed. People who use Pascal for serious programming fall into a fatal trap. Because the language is impotent, it must be extended. But each group extends Pascal in its own direction, to make it look like whatever language they really want. Extensions for separate compilation, FORTRAN-like COMMON, string data types, internal static variables, initia