Package Hierarchy

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 2796 Experts worldwide ranked by ideXlab platform

Michael D Diathesopoulos - One of the best experts on this subject based on the ideXlab platform.

  • competition law and sector regulation in the european energy market after the third energy Package Hierarchy and efficiency
    Social Science Research Network, 2011
    Co-Authors: Michael D Diathesopoulos
    Abstract:

    The aim of this research is to provide the basic parameters for a model for the definition of the relation between the general competition and sector specific frameworks and rules regarding the regulation of the Internal Energy Market, especially after the Third Energy Package. The research considers the recent sector specific framework in relation to a series of recent competition law cases of the Energy Market where structural remedies were applied under the commitments procedure.Essential facilities doctrine and generally competition law tools do not seem to provide a suitable framework for effectively addressing the dynamic competition concept, treating the issue of balancing incentives to invest with open market concept and designing solutions for the stable development of Energy Market infrastructure. Competition law provides ex post and case-by-case solutions, which lack the breadth of objectives expressed by sector regulation. On the other hand, sector regulation seems to incorporate competition rules and objectives, while the application of competition law in recent decisions did not seem to take into consideration present and forthcoming sector-specific context and parameters. However, competition law has a hierarchical priority over sector-specific rules and its direct application cannot be excluded when sector regulation is insufficient or is not applied efficiently. Sector rules should have a functional priority regarding their implementation as lex specialis and constitute the context for any potential application of competition law. Furthermore, structural interventions based on competition rules will abide by the principle of proportionality, only in specific cases where market organisation and poor regulatory supervision allow the continuation of high vertical integration and anticompetitive practices. There is also a need to establish an efficient model of clear allocation of duties between Competition Authorities and Sector Regulators.The model proposed by the research emphasizes prioritization of sector-specific rules, use of competition rules as an interpretative tool, limitation of their independent application to cases where sector regulation fails and even then after taking into consideration sector specific context and acceptance of dynamic competition as an orientating framework for the regulation of the Internal Energy Market.

Andy Leonard - One of the best experts on this subject based on the ideXlab platform.

Balogh Gergő - One of the best experts on this subject based on the ideXlab platform.

David Svoboda - One of the best experts on this subject based on the ideXlab platform.

  • the cert oracle secure coding standard for java
    2011
    Co-Authors: Fred Long, Robert C Seacord, Dhruv Mohindra, Dean F Sutherland, David Svoboda
    Abstract:

    In the Java world, security is not viewed as an add-on a feature. It is a pervasive way of thinking. Those who forget to think in a secure mindset end up in trouble. But just because the facilities are there doesnt mean that security is assured automatically. A set of standard practices has evolved over the years. The Secure Coding Standard for Java is a compendium of these practices. These are not theoretical research papers or product marketing blurbs. This is all serious, mission-critical, battle-tested, enterprise-scale stuff. James A. Gosling, Father of the Java Programming Language An essential element of secure coding in the Java programming language is a well-documented and enforceable coding standard. Coding standards encourage programmers to follow a uniform set of rules determined by the requirements of the project and organization, rather than by the programmers familiarity or preference. Once established, these standards can be used as a metric to evaluate source code (using manual or automated processes). The CERT Oracle Secure Coding Standard for Java provides rules designed to eliminate insecure coding practices that can lead to exploitable vulnerabilities. Application of the standards guidelines will lead to higher-quality systemsrobust systems that are more resistant to attack. Such guidelines are required for the wide range of products coded in Javafor devices such as PCs, game players, mobile phones, home appliances, and automotive electronics. After a high-level introduction to Java application security, seventeen consistently organized chapters detail specific rules for key areas of Java development. For each area, the authors present noncompliant examples and corresponding compliant solutions, show how to assess risk, and offer references for further information. Each rule is prioritized based on the severity of consequences, likelihood of introducing exploitable vulnerabilities, and cost of remediation. The standard provides secure coding rules for the Java SE 6 Platform including the Java programming language and libraries, and also addresses new features of the Java SE 7 Platform. It describes language behaviors left to the discretion of JVM and compiler implementers, guides developers in the proper use of Javas APIs and security architecture, and considers security concerns pertaining to standard extension APIs (from the javax Package Hierarchy).The standard covers security issues applicable to these libraries: lang, util, Collections, Concurrency Utilities, Logging, Management, Reflection, Regular Expressions, Zip, I/O, JMX, JNI, Math, Serialization, and JAXP.

Fred Long - One of the best experts on this subject based on the ideXlab platform.

  • the cert oracle secure coding standard for java
    2011
    Co-Authors: Fred Long, Robert C Seacord, Dhruv Mohindra, Dean F Sutherland, David Svoboda
    Abstract:

    In the Java world, security is not viewed as an add-on a feature. It is a pervasive way of thinking. Those who forget to think in a secure mindset end up in trouble. But just because the facilities are there doesnt mean that security is assured automatically. A set of standard practices has evolved over the years. The Secure Coding Standard for Java is a compendium of these practices. These are not theoretical research papers or product marketing blurbs. This is all serious, mission-critical, battle-tested, enterprise-scale stuff. James A. Gosling, Father of the Java Programming Language An essential element of secure coding in the Java programming language is a well-documented and enforceable coding standard. Coding standards encourage programmers to follow a uniform set of rules determined by the requirements of the project and organization, rather than by the programmers familiarity or preference. Once established, these standards can be used as a metric to evaluate source code (using manual or automated processes). The CERT Oracle Secure Coding Standard for Java provides rules designed to eliminate insecure coding practices that can lead to exploitable vulnerabilities. Application of the standards guidelines will lead to higher-quality systemsrobust systems that are more resistant to attack. Such guidelines are required for the wide range of products coded in Javafor devices such as PCs, game players, mobile phones, home appliances, and automotive electronics. After a high-level introduction to Java application security, seventeen consistently organized chapters detail specific rules for key areas of Java development. For each area, the authors present noncompliant examples and corresponding compliant solutions, show how to assess risk, and offer references for further information. Each rule is prioritized based on the severity of consequences, likelihood of introducing exploitable vulnerabilities, and cost of remediation. The standard provides secure coding rules for the Java SE 6 Platform including the Java programming language and libraries, and also addresses new features of the Java SE 7 Platform. It describes language behaviors left to the discretion of JVM and compiler implementers, guides developers in the proper use of Javas APIs and security architecture, and considers security concerns pertaining to standard extension APIs (from the javax Package Hierarchy).The standard covers security issues applicable to these libraries: lang, util, Collections, Concurrency Utilities, Logging, Management, Reflection, Regular Expressions, Zip, I/O, JMX, JNI, Math, Serialization, and JAXP.