Find the standard you are looking for at Engineering360. Documents are available for purchase from the IHS Standards Store.

1 - 14 of 14 results

ICAO 10047 - AVIATION SECURITY OVERSIGHT MANUAL - FIRST EDITION; CORRIGENDA 1 05/29/2016 Organization: ICAO
Date: 2015-01-01
Description: With respect to aviation security, it is particularly important to maintain uniformity in the effectiveness of worldwide standards, since the level of protection against acts of unlawful interference deriving from the implementation of security measures as stipulated in the international Standards and Recommended Practices (SARPs) is only as strong as the weakest link in the global aviation network. The implementation of security-related SARPs by a Member State should be effected under the rule of law promulgated in that State.
ASTM E2147 - STANDARD SPECIFICATION FOR AUDIT AND DISCLOSURE LOGS FOR USE IN HEALTH INFORMATION SYSTEMS Organization: ASTM
Date: 2001-11-10
Description: This specification is for the development and implementation of security audit/disclosure logs for health information.
ASTM PS115 - PROVISIONAL STANDARD SPECIFICATION FOR AUDIT AND DISCLOSURE LOGS FOR USE IN HEALTH INFORMATION SYSTEMS Organization: ASTM
Date: 1999-03-10
Description: Scope 1.1 This provisional specification is for the development and implementation of security audit/disclosure logs for health information.
DSF/PREN 50126-5 - RAILWAY APPLICATIONS - THE SPECIFICATION AND DEMONSTRATION OF RELIABILITY, AVAILABILITY, MAINTAINABILITY AND SAFETY (RAMS) -- PART 5: FUNCTIONAL SAFETY - SOFTWARE Organization: DS
Description: This part EN 50126 is applicable - to the specification and demonstration of safety for all software in railway applications and at all levels of such an application, as appropriate, from complete railway systems to major systems and to individual and combined sub-systems within these major systems; in particular: - to new systems; - to new systems integrated into existing systems in operation prior to the creation of this European Standard, although it is not generally applicable to other aspects of the existing system; - for modifications of existing software on systems in operation prior to the creation of this European Standard, although it is not generally applicable to other aspects of the existing system. - at all relevant p 13226 hases of the lifecycle of an application; - for use by railway duty holders, railway suppliers, assessors and safety authorities; - to all safety related software used in railway control and protection systems, including 1. application programming, 2. operating systems, 3. support tools, 4. firmware.
BSI - PREN 50126-5 - RAILWAY APPLICATIONS - THE SPECIFICATION AND DEMONSTRATION OF RELIABILITY, AVAILABILITY, MAINTAINABILITY AND SAFETY (RAMS) - PART 5: FUNCTIONAL SAFETY - SOFTWARE Organization: BSI
Date: 2012-10-01
Description: As a minimum, evidence shall be provided in such cases to demonstrate: - either that the software is not relied on for safety, - or that the software can be relied on for those functions which relate to safety; • applies - to the specification, architecture, design, development, implementation, integration, installation, acceptance, deployment, operation, maintenance and modification/extension phases of the software in a system /subsystem.
DSF/PREN 50126-4 - RAILWAY APPLICATIONS - THE SPECIFICATION AND DEMONSTRATION OF RELIABILITY, AVAILABILITY, MAINTAINABILITY AND SAFETY (RAMS) -- PART 4: FUNCTIONAL SAFETY - ELECTRICAL/ELECTRONIC/PROGRAMMABLE ELECTRONIC SYSTEMS Organization: DS
Description: . - to generic sub-systems and hardware (both application-independent and those intended for a particular class of application), and also to systems/sub-systems/hardware for specific applications; - addresses railway specifics; - does not define - RAMS targets, quantities, requirements or solutions for specific railway applications - rules or processes pertaining to the certification of railway products against the requirements of this standard - an approval process by the safety authority; - does not specify requirements for ensuring system security.
BSI - PREN 50126-4 - RAILWAY APPLICATIONS - THE SPECIFICATION AND DEMONSTRATION OF RELIABILITY, AVAILABILITY, MAINTAINABILITY AND SAFETY (RAMS) - PART 4: FUNCTIONAL SAFETY - ELECTRICAL/ELECTRONIC/PROGRAMMABLE ELECTRONIC SYSTEMS Organization: BSI
Date: 2012-10-01
Description: As a minimum, evidence shall be provided in such cases to demonstrate: - either that the hardware is not relied on for safety, - or that the hardware can be relied on for those functions which relate to safety; • applies - to the specification, architecture, design, construction, implementation, integration, manufacturing, installation, acceptance, operation, maintenance and modification/extension phases of the system /subsystem and hardware, and also to individual sub-systems and hardware within the overall system as determined by the process in EN 50126-1 and supported by the methods in EN 50126-2.
CLSI AUTO10 - AUTOVERIFICATION OF CLINICAL LABORATORY TEST RESULTS; APPROVED GUIDELINE - FIRST EDITION; VOL 26; NO 32 Organization: CLSI
Date: 2006-10-01
Description: For additional information, refer to the current edition of CLSI document AUTO11—IT Security of In Vitro Diagnostic Instruments and Software Systems.
ETSI - TS 103 161-16 - ACCESS, TERMINALS, TRANSMISSION AND MULTIPLEXING (ATTM); INTEGRATED BROADBAND CABLE AND TELEVISION NETWORKS; IPCABLECOM 1.5; PART 16: SIGNALLING FOR CALL MANAGEMENT SERVER - V1.1.1 Organization: ETSI
Date: 2011-04-01
Description: These documents cover areas such as: Event Message recording for billing and other back office functions [23]; Dynamic Quality of Service [21]; Operations and Provisioning [i.8]; Electronic Surveillance [22]; and Security [26]. These other specifications indirectly place requirements on the signalling protocol to ensure that it transports the correct data needed to implement a complete system.
ETSI - GS ECI 001-1 - EMBEDDED COMMON INTERFACE (ECI) FOR EXCHANGEABLE CA/DRM SOLUTIONS; PART 1: ARCHITECTURE, DEFINITIONS AND OVERVIEW - V1.1.1 Organization: ETSI
Date: 2014-09-01
Description: The present document addresses an architecture and an overview of the relevant interface specifications for the implementation of interoperable CA/DRM systems in CPEs. The ECI specification only applies to the reception and further processing of content which is controlled by a Conditional Access and/or Digital Rights Management system and has been scrambled by the service provider.
ETSI - GS ECI 001-2 - EMBEDDED COMMON INTERFACE (ECI) FOR EXCHANGEABLE CA/DRM SOLUTIONS; PART 2: USE CASES AND REQUIREMENTS - V1.1.1 Organization: ETSI
Date: 2014-09-01
Description: The present document addresses use cases and requirements as basis for the implementation of interoperable CA/DRM systems in CPEs.
ITU-T J.178 - IPCABLECOM CMS TO CMS SIGNALLING - STUDY GROUP 9 Organization: ITU-T
Date: 2005-11-01
Description: J.167); and Security (ITU-T Rec. J.170). These other specifications indirectly place requirements on the signalling protocol to ensure that it transports the correct data needed to implement a complete system.
ISO/IEC 29341-18-13 - INFORMATION TECHNOLOGY – UPNP DEVICE ARCHITECTURE – PART 18-13: REMOTE ACCESS DEVICE CONTROL PROTOCOL – REMOTE ACCESS TRANSPORT AGENT CONFIGURATION SERVICE - FIRST EDITION Organization: ISO
Date: 2011-08-01
Description: These keywords are thus capitalized when used to unambiguously specify requirements over protocol and application features and behavior that affect the interoperability and security of implementations. When these words are not capitalized, they are meant in their natural-language sense.
ISO/IEC 29341-18-4 - INFORMATION TECHNOLOGY – UPNP DEVICE ARCHITECTURE – PART 18-4: REMOTE ACCESS DEVICE CONTROL PROTOCOL – REMOTE ACCESS DISCOVERY AGENT DEVICE - FIRST EDITION Organization: ISO
Date: 2011-08-01
Description: These keywords are thus capitalized when used to unambiguously specify requirements over protocol and application features and behavior that affect the interoperability and security of implementations. When these words are not capitalized, they are meant in their natural-language sense.

1 - 14 of 14 results