Building Secure and Reliable Systems. Best Practices for Designing, Implementing, and Maintaining Systems

- Autorzy:
- Heather Adkins, Betsy Beyer, Paul Blankinship
- Promocja Przejdź


- Ocena:
- Bądź pierwszym, który oceni tę książkę
- Stron:
- 558
- Dostępne formaty:
-
ePubMobi
Opis książki: Building Secure and Reliable Systems. Best Practices for Designing, Implementing, and Maintaining Systems
Can a system be considered truly reliable if it isn't fundamentally secure? Or can it be considered secure if it's unreliable? Security is crucial to the design and operation of scalable systems in production, as it plays an important part in product quality, performance, and availability. In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure.
Two previous O’Reilly books from Google—Site Reliability Engineering and The Site Reliability Workbook—demonstrated how and why a commitment to the entire service lifecycle enables organizations to successfully build, deploy, monitor, and maintain software systems. In this latest guide, the authors offer insights into system design, implementation, and maintenance from practitioners who specialize in security and reliability. They also discuss how building and adopting their recommended best practices requires a culture that’s supportive of such change.
You’ll learn about secure and reliable systems through:
- Design strategies
- Recommendations for coding, testing, and debugging practices
- Strategies to prepare for, respond to, and recover from incidents
- Cultural best practices that help teams across your organization collaborate effectively
Wybrane bestsellery
-
In 2016, Google’s Site Reliability Engineering book ignited an industry discussion on what it means to run production services today—and why reliability considerations are fundamental to service design. Now, Google engineers who worked on that bestseller introduce The Site Reliability...
The Site Reliability Workbook. Practical Ways to Implement SRE The Site Reliability Workbook. Practical Ways to Implement SRE
(0,00 zł najniższa cena z 30 dni)169.15 zł
199.00 zł(-15%) -
Jeśli chcesz zrozumieć filozofię SRE, trzymasz w ręku właściwą, choć nietypową książkę. Jest to zbiór najciekawszych esejów i artykułów autorstwa osób odpowiedzialnych za SRE w Google. Z lektury tych esejów dowiesz się, w jaki sposób zaangażowanie w cały cykl życia oprogramowania umożliwił skutec...
Site Reliability Engineering. Jak Google zarządza systemami producyjnymi Site Reliability Engineering. Jak Google zarządza systemami producyjnymi
Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
(0,00 zł najniższa cena z 30 dni)47.40 zł
79.00 zł(-40%) -
The overwhelming majority of a software systemâ??s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articl...
Site Reliability Engineering. How Google Runs Production Systems Site Reliability Engineering. How Google Runs Production Systems
(0,00 zł najniższa cena z 30 dni)203.15 zł
239.00 zł(-15%) -
Ta książka jest kompleksowym i praktycznym przewodnikiem po hakowaniu aplikacji internetowych w ramach udziału w programach bug bounty. Znajdziesz w niej wszystkie niezbędne informacje, od budowania relacji z klientami i pisania znakomitych raportów o błędach w zabezpieczeniach po naukę zaawansow...
Bug Bounty Bootcamp. Przewodnik po tropieniu i zgłaszaniu luk w zabezpieczeniach Bug Bounty Bootcamp. Przewodnik po tropieniu i zgłaszaniu luk w zabezpieczeniach
(0,00 zł najniższa cena z 30 dni)64.35 zł
99.00 zł(-35%) -
Ta książka powstała z myślą o architektach oprogramowania, projektantach, programistach i dyrektorach do spraw technicznych. Zwięźle i przystępnie opisano w niej, jak zadbać o bezpieczeństwo na wczesnym etapie projektowania oprogramowania i jak zaangażować w ten proces cały team. Najpierw zapreze...
Po pierwsze: bezpieczeństwo. Przewodnik dla twórców oprogramowania Po pierwsze: bezpieczeństwo. Przewodnik dla twórców oprogramowania
(0,00 zł najniższa cena z 30 dni)51.35 zł
79.00 zł(-35%) -
Ta książka stanowi wszechstronny i praktyczny przegląd dziedziny bezpieczeństwa informacji. Posłuży każdemu, kto jest zainteresowany tą dziedziną, chce zdobyć ogólną wiedzę na ten temat albo zastanawia się, od czego zacząć wdrażanie systemu bezpieczeństwa we własnej organizacji. Znalazły się tuta...
Podstawy bezpieczeństwa informacji. Praktyczne wprowadzenie Podstawy bezpieczeństwa informacji. Praktyczne wprowadzenie
(0,00 zł najniższa cena z 30 dni)38.35 zł
59.00 zł(-35%) -
Ta książka stanowi kurs praktycznych technik hakowania, dzięki którym dokładnie poznasz zasady i narzędzia używane do przełamywania zabezpieczeń i uzyskiwania dostępu do chronionych danych. Dowiesz się, w jaki sposób należy się przygotować do przeprowadzenia ataku, a także jakie aspekty infrastru...
Warsztat hakera. Testy penetracyjne i inne techniki wykrywania podatności Warsztat hakera. Testy penetracyjne i inne techniki wykrywania podatności
(0,00 zł najniższa cena z 30 dni)64.35 zł
99.00 zł(-35%) -
To przystępny i kompleksowy przewodnik po zagadnieniach bezpieczeństwa, skierowany do osób, które nie znają się na komputerach i informatyce. Kwestie cyberbezpieczeństwa przedstawiono tu krok po kroku, z minimalnym użyciem specjalistycznego języka. Opisano dziesiątki całkiem prostych sposobów poz...
Firewall nie powstrzyma prawdziwego smoka, czyli jak zadbać o cyberbezpieczeństwo. Przewodnik dla niefachowców. Wydanie III Firewall nie powstrzyma prawdziwego smoka, czyli jak zadbać o cyberbezpieczeństwo. Przewodnik dla niefachowców. Wydanie III
(0,00 zł najniższa cena z 30 dni)29.40 zł
49.00 zł(-40%) -
Znasz film Złap mnie, jeśli potrafisz? To nie jest historia wyssana z palca, ale opowieść, której bohaterem jest autor tej książki! Nowoczesne technologie dostarczyły wielu ekscytujących możliwości. Nie tylko Tobie, ale także całej rzeszy kanciarzy i oszustów, którzy ze wszystkich sił starają się...
Oszukaj mnie, jeśli potrafisz. Proste sposoby przechytrzenia współczesnych kanciarzy Oszukaj mnie, jeśli potrafisz. Proste sposoby przechytrzenia współczesnych kanciarzy
(0,00 zł najniższa cena z 30 dni)13.90 zł
44.90 zł(-69%) -
Ta książka to praktyczny przewodnik po aktywnych technikach wykrywania, analizowania i neutralizowania zagrożeń cybernetycznych. Dzięki niej, nawet jeśli nie posiadasz specjalistycznej wiedzy w tym zakresie, łatwo wdrożysz od podstaw skuteczny program aktywnego zabezpieczania swojej organizacji. ...
Aktywne wykrywanie zagrożeń w systemach IT w praktyce. Wykorzystywanie analizy danych, frameworku ATT&CK oraz narzędzi open source Aktywne wykrywanie zagrożeń w systemach IT w praktyce. Wykorzystywanie analizy danych, frameworku ATT&CK oraz narzędzi open source
(0,00 zł najniższa cena z 30 dni)57.85 zł
89.00 zł(-35%)
Ebooka przeczytasz na:
-
czytnikach Inkbook, Kindle, Pocketbook i innych
-
systemach Windows, MacOS i innych
-
systemach Windows, Android, iOS, HarmonyOS
-
na dowolnych urządzeniach i aplikacjach obsługujących formaty: PDF, EPub, Mobi
Masz pytania? Zajrzyj do zakładki Pomoc »
Audiobooka posłuchasz:
-
w aplikacji Ebookpoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych
-
na dowolonych urządzeniach i aplikacjach obsługujących format MP3 (pliki spakowane w ZIP)
Masz pytania? Zajrzyj do zakładki Pomoc »
Kurs Video zobaczysz:
-
w aplikacji Ebookpoint na Android, iOS, HarmonyOs
-
na systemach Windows, MacOS i innych
-
na dowolonych urządzeniach i aplikacjach obsługujących format MP4 (pliki spakowane w ZIP)
Szczegóły książki
- ISBN Ebooka:
- 978-14-920-8307-8, 9781492083078
- Data wydania ebooka:
-
2020-03-16
Data wydania ebooka często jest dniem wprowadzenia tytułu do sprzedaży i może nie być równoznaczna z datą wydania książki papierowej. Dodatkowe informacje możesz znaleźć w darmowym fragmencie. Jeśli masz wątpliwości skontaktuj się z nami sklep@helion.pl.
- Język publikacji:
- angielski
- Rozmiar pliku ePub:
- 5.3MB
- Rozmiar pliku Mobi:
- 12.4MB
- Kategorie:
Hacking » Bezpieczeństwo systemów
Spis treści książki
- Foreword by Royal Hansen
- Foreword by Michael Wildpaner
- Preface
- Why We Wrote This Book
- Who This Book Is For
- A Note About Culture
- How to Read This Book
- Conventions Used in This Book
- OReilly Online Learning
- How to Contact Us
- Acknowledgments
- I. Introductory Material
- 1. The Intersection of Security and Reliability
- On Passwords and Power Drills
- Reliability Versus Security: Design Considerations
- Confidentiality, Integrity, Availability
- Confidentiality
- Integrity
- Availability
- Reliability and Security: Commonalities
- Invisibility
- Assessment
- Simplicity
- Evolution
- Resilience
- From Design to Production
- Investigating Systems and Logging
- Crisis Response
- Recovery
- Conclusion
- 2. Understanding Adversaries
- Attacker Motivations
- Attacker Profiles
- Hobbyists
- Vulnerability Researchers
- Governments and Law Enforcement
- Intelligence gathering
- Military purposes
- Policing domestic activity
- Protecting your systems from nation-state actors
- Activists
- Protecting your systems from hacktivists
- Criminal Actors
- Protecting your systems from criminal actors
- Automation and Artificial Intelligence
- Protecting your systems from automated attacks
- Insiders
- First-party insiders
- Third-party insiders
- Related insiders
- Threat modeling insider risk
- Designing for insider risk
- Attacker Methods
- Threat Intelligence
- Cyber Kill Chains
- Tactics, Techniques, and Procedures
- Risk Assessment Considerations
- Conclusion
- II. Designing Systems
- 3. Case Study: Safe Proxies
- Safe Proxies in Production Environments
- Google Tool Proxy
- Conclusion
- 4. Design Tradeoffs
- Design Objectives and Requirements
- Feature Requirements
- Nonfunctional Requirements
- Features Versus Emergent Properties
- Example: Google Design Document
- Design Objectives and Requirements
- Balancing Requirements
- Example: Payment Processing
- Security and reliability considerations
- Using a third-party service provider to handle sensitive data
- Benefits
- Costs and nontechnical risks
- Reliability risks
- Security risks
- Example: Payment Processing
- Managing Tensions and Aligning Goals
- Example: Microservices and the Google Web Application Framework
- Aligning Emergent-Property Requirements
- Initial Velocity Versus Sustained Velocity
- Conclusion
- 5. Design for Least Privilege
- Concepts and Terminology
- Least Privilege
- Zero Trust Networking
- Zero Touch
- Concepts and Terminology
- Classifying Access Based on Risk
- Best Practices
- Small Functional APIs
- Breakglass
- Auditing
- Collecting good audit logs
- Choosing an auditor
- Testing and Least Privilege
- Testing of least privilege
- Testing with least privilege
- Diagnosing Access Denials
- Graceful Failure and Breakglass Mechanisms
- Worked Example: Configuration Distribution
- POSIX API via OpenSSH
- Software Update API
- Custom OpenSSH ForceCommand
- Custom HTTP Receiver (Sidecar)
- Custom HTTP Receiver (In-Process)
- Tradeoffs
- A Policy Framework for Authentication and Authorization Decisions
- Using Advanced Authorization Controls
- Investing in a Widely Used Authorization Framework
- Avoiding Potential Pitfalls
- Advanced Controls
- Multi-Party Authorization (MPA)
- Three-Factor Authorization (3FA)
- Business Justifications
- Temporary Access
- Proxies
- Tradeoffs and Tensions
- Increased Security Complexity
- Impact on Collaboration and Company Culture
- Quality Data and Systems That Impact Security
- Impact on User Productivity
- Impact on Developer Complexity
- Conclusion
- 6. Design for Understandability
- Why Is Understandability Important?
- System Invariants
- Analyzing Invariants
- Mental Models
- Why Is Understandability Important?
- Designing Understandable Systems
- Complexity Versus Understandability
- Breaking Down Complexity
- Centralized Responsibility for Security and Reliability Requirements
- System Architecture
- Understandable Interface Specifications
- Prefer narrow interfaces that offer less room for interpretation
- Prefer interfaces that enforce a common object model
- Pay attention to idempotent operations
- Understandable Interface Specifications
- Understandable Identities, Authentication, and Access Control
- Identities
- Example: Identity model for the Google production system
- Identities
- Authentication and transport security
- Access control
- Security Boundaries
- Small TCBs and strong security boundaries
- Security boundaries and threat models
- TCBs and understandability
- Software Design
- Using Application Frameworks for Service-Wide Requirements
- Understanding Complex Data Flows
- Considering API Usability
- Example: Secure cryptographic APIs and the Tink crypto framework
- Conclusion
- 7. Design for a Changing Landscape
- Types of Security Changes
- Designing Your Change
- Architecture Decisions to Make Changes Easier
- Keep Dependencies Up to Date and Rebuild Frequently
- Release Frequently Using Automated Testing
- Use Containers
- Use Microservices
- Example: Googles frontend design
- Different Changes: Different Speeds, Different Timelines
- Short-Term Change: Zero-Day Vulnerability
- Example: Shellshock
- Short-Term Change: Zero-Day Vulnerability
- Medium-Term Change: Improvement to Security Posture
- Example: Strong second-factor authentication using FIDO security keys
- Long-Term Change: External Demand
- Example: Increasing HTTPS usage
- Complications: When Plans Change
- Example: Growing ScopeHeartbleed
- Conclusion
- 8. Design for Resilience
- Design Principles for Resilience
- Defense in Depth
- The Trojan Horse
- Threat modeling and vulnerability discovery
- Deployment of the attack
- Execution of the attack
- Compromise
- The Trojan Horse
- Google App Engine Analysis
- Risky APIs
- Runtime layers
- Controlling Degradation
- Differentiate Costs of Failures
- Computing resources
- User experience
- Speed of mitigation
- Differentiate Costs of Failures
- Deploy Response Mechanisms
- Load shedding
- Throttling
- Automated response
- Automate Responsibly
- Failing safe versus failing secure
- A foothold for humans
- Controlling the Blast Radius
- Role Separation
- Location Separation
- Aligning physical and logical architecture
- Isolation of trust
- Limitations of location-based trust
- Isolation of confidentiality
- Time Separation
- Failure Domains and Redundancies
- Failure Domains
- Functional isolation
- Data isolation
- Practical aspects
- Failure Domains
- Component Types
- High-capacity components
- High-availability components
- Low-dependency components
- Controlling Redundancies
- Failover strategies
- Common pitfalls
- Continuous Validation
- Validation Focus Areas
- Validation in Practice
- Inject anticipated changes of behavior
- Exercise emergency components as part of normal workflows
- Split when you cannot mirror traffic
- Oversubscribe but prevent complacency
- Measure key rotation cycles
- Practical Advice: Where to Begin
- Conclusion
- 9. Design for Recovery
- What Are We Recovering From?
- Random Errors
- Accidental Errors
- Software Errors
- Malicious Actions
- What Are We Recovering From?
- Design Principles for Recovery
- Design to Go as Quickly as Possible (Guarded by Policy)
- Limit Your Dependencies on External Notions of Time
- Rollbacks Represent a Tradeoff Between Security and Reliability
- Deny lists
- Minimum Acceptable Security Version Numbers
- Rotating signing keys
- Rolling back firmware and other hardware-centric constraints
- Use an Explicit Revocation Mechanism
- A centralized service to revoke certificates
- Failing open
- Handling emergencies directly
- Removing dependency on accurate notions of time
- Revoking credentials at scale
- Avoiding risky exceptions
- Know Your Intended State, Down to the Bytes
- Host management
- Device firmware
- Global services
- Persistent data
- Design for Testing and Continuous Validation
- Emergency Access
- Access Controls
- Communications
- Responder Habits
- Unexpected Benefits
- Conclusion
- 10. Mitigating Denial-of-Service Attacks
- Strategies for Attack and Defense
- Attackers Strategy
- Defenders Strategy
- Strategies for Attack and Defense
- Designing for Defense
- Defendable Architecture
- Defendable Services
- Mitigating Attacks
- Monitoring and Alerting
- Graceful Degradation
- A DoS Mitigation System
- Strategic Response
- Dealing with Self-Inflicted Attacks
- User Behavior
- Client Retry Behavior
- Conclusion
- III. Implementing Systems
- 11. Case Study: Designing, Implementing, and Maintaining a Publicly Trusted CA
- Background on Publicly Trusted Certificate Authorities
- Why Did We Need a Publicly Trusted CA?
- The Build or Buy Decision
- Design, Implementation, and Maintenance Considerations
- Programming Language Choice
- Complexity Versus Understandability
- Securing Third-Party and Open Source Components
- Testing
- Resiliency for the CA Key Material
- Data Validation
- Conclusion
- 12. Writing Code
- Frameworks to Enforce Security and Reliability
- Benefits of Using Frameworks
- Example: Framework for RPC Backends
- Example code snippets
- Frameworks to Enforce Security and Reliability
- Common Security Vulnerabilities
- SQL Injection Vulnerabilities: TrustedSqlString
- Preventing XSS: SafeHtml
- Lessons for Evaluating and Building Frameworks
- Simple, Safe, Reliable Libraries for Common Tasks
- Rollout Strategy
- Incremental rollout
- Legacy conversions
- Simplicity Leads to Secure and Reliable Code
- Avoid Multilevel Nesting
- Eliminate YAGNI Smells
- Repay Technical Debt
- Refactoring
- Security and Reliability by Default
- Choose the Right Tools
- Use memory-safe languages
- Use strong typing and static type checking
- Choose the Right Tools
- Use Strong Types
- Sanitize Your Code
- C++: Valgrind or Google Sanitizers
- Go: Race Detector
- Conclusion
- 13. Testing Code
- Unit Testing
- Writing Effective Unit Tests
- When to Write Unit Tests
- How Unit Testing Affects Code
- Unit Testing
- Integration Testing
- Writing Effective Integration Tests
- Dynamic Program Analysis
- Fuzz Testing
- How Fuzz Engines Work
- Writing Effective Fuzz Drivers
- An Example Fuzzer
- Continuous Fuzzing
- Example: ClusterFuzz and OSSFuzz
- Static Program Analysis
- Automated Code Inspection Tools
- Integration of Static Analysis in the Developer Workflow
- Abstract Interpretation
- Formal Methods
- Conclusion
- 14. Deploying Code
- Concepts and Terminology
- Threat Model
- Best Practices
- Require Code Reviews
- Rely on Automation
- Verify Artifacts, Not Just People
- Treat Configuration as Code
- Securing Against the Threat Model
- Advanced Mitigation Strategies
- Binary Provenance
- What to put in binary provenance
- Binary Provenance
- Provenance-Based Deployment Policies
- Implementing policy decisions
- Verifiable Builds
- Verifiable build architectures
- Implementing verifiable builds
- Untrusted inputs
- Unauthenticated inputs
- Deployment Choke Points
- Post-Deployment Verification
- Practical Advice
- Take It One Step at a Time
- Provide Actionable Error Messages
- Ensure Unambiguous Provenance
- Create Unambiguous Policies
- Include a Deployment Breakglass
- Securing Against the Threat Model, Revisited
- Conclusion
- 15. Investigating Systems
- From Debugging to Investigation
- Example: Temporary Files
- Debugging Techniques
- Distinguish horses from zebras
- Set aside time for debugging and investigations
- Record your observations and expectations
- Know whats normal for your system
- Reproduce the bug
- Isolate the problem
- Be mindful of correlation versus causation
- Test your hypotheses with actual data
- Reread the docs
- Practice!
- What to Do When Youre Stuck
- Improve observability
- Take a break
- Clean up code
- Delete it!
- Stop when things start to go wrong
- Improve access and authorization controls, even for nonsensitive systems
- From Debugging to Investigation
- Collaborative Debugging: A Way to Teach
- How Security Investigations and Debugging Differ
- Collect Appropriate and Useful Logs
- Design Your Logging to Be Immutable
- Take Privacy into Consideration
- Determine Which Security Logs to Retain
- Operating system logs
- Host agents
- Application logs
- Cloud logs
- Network-based logging and detection
- Budget for Logging
- Robust, Secure Debugging Access
- Reliability
- Security
- Conclusion
- IV. Maintaining Systems
- 16. Disaster Planning
- Defining Disaster
- Dynamic Disaster Response Strategies
- Disaster Risk Analysis
- Setting Up an Incident Response Team
- Identify Team Members and Roles
- Establish a Team Charter
- Establish Severity and Priority Models
- Define Operating Parameters for Engaging the IR Team
- Develop Response Plans
- Create Detailed Playbooks
- Ensure Access and Update Mechanisms Are in Place
- Prestaging Systems and People Before an Incident
- Configuring Systems
- Training
- Processes and Procedures
- Testing Systems and Response Plans
- Auditing Automated Systems
- Conducting Nonintrusive Tabletops
- Testing Response in Production Environments
- Single system testing/fault injection
- Human resource testing
- Multicomponent testing
- System-wide failures/failovers
- Red Team Testing
- Evaluating Responses
- Google Examples
- Test with Global Impact
- DiRT Exercise Testing Emergency Access
- Industry-Wide Vulnerabilities
- Conclusion
- 17. Crisis Management
- Is It a Crisis or Not?
- Triaging the Incident
- Compromises Versus Bugs
- Is It a Crisis or Not?
- Taking Command of Your Incident
- The First Step: Dont Panic!
- Beginning Your Response
- Establishing Your Incident Team
- Operational Security
- Trading Good OpSec for the Greater Good
- The Investigative Process
- Sharding the investigation
- Keeping Control of the Incident
- Parallelizing the Incident
- Handovers
- Morale
- Communications
- Misunderstandings
- Hedging
- Meetings
- Keeping the Right People Informed with the Right Levels of Detail
- Putting It All Together
- Triage
- Declaring an Incident
- Communications and Operational Security
- Beginning the Incident
- Handover
- Handing Back the Incident
- Preparing Communications and Remediation
- Closure
- Conclusion
- 18. Recovery and Aftermath
- Recovery Logistics
- Recovery Timeline
- Planning the Recovery
- Scoping the Recovery
- Recovery Considerations
- How will your attacker respond to your recovery effort?
- Is your recovery infrastructure or tooling compromised?
- What variants of the attack exist?
- Will your recovery reintroduce attack vectors?
- What are your mitigation options?
- Recovery Checklists
- Initiating the Recovery
- Isolating Assets (Quarantine)
- System Rebuilds and Software Upgrades
- Data Sanitization
- Recovery Data
- Credential and Secret Rotation
- After the Recovery
- Postmortems
- Examples
- Compromised Cloud Instances
- Large-Scale Phishing Attack
- Targeted Attack Requiring Complex Recovery
- Conclusion
- V. Organization and Culture
- 19. Case Study: Chrome Security Team
- Background and Team Evolution
- Security Is a Team Responsibility
- Help Users Safely Navigate the Web
- Speed Matters
- Design for Defense in Depth
- Be Transparent and Engage the Community
- Conclusion
- 20. Understanding Roles and Responsibilities
- Who Is Responsible for Security and Reliability?
- The Roles of Specialists
- Understanding Security Expertise
- Certifications and Academia
- Who Is Responsible for Security and Reliability?
- Integrating Security into the Organization
- Embedding Security Specialists and Security Teams
- Example: Embedding Security at Google
- Special Teams: Blue and Red Teams
- External Researchers
- Conclusion
- 21. Building a Culture of Security and Reliability
- Defining a Healthy Security and Reliability Culture
- Culture of Security and Reliability by Default
- Culture of Review
- Culture of Awareness
- Culture of Yes
- Culture of Inevitably
- Culture of Sustainability
- Defining a Healthy Security and Reliability Culture
- Changing Culture Through Good Practice
- Align Project Goals and Participant Incentives
- Reduce Fear with Risk-Reduction Mechanisms
- Make Safety Nets the Norm
- Increase Productivity and Usability
- Overcommunicate and Be Transparent
- Build Empathy
- Convincing Leadership
- Understand the Decision-Making Process
- Build a Case for Change
- Pick Your Battles
- Escalations and Problem Resolution
- Conclusion
- Conclusion
- A. A Disaster Risk Assessment Matrix
- Index
O'Reilly Media - inne książki
-
FinOps brings financial accountability to the variable spend model of cloud. Used by the majority of global enterprises, this management practice has grown from a fringe activity to the de facto discipline managing cloud spend. In this book, authors J.R. Storment and Mike Fuller outline the proce...(0,00 zł najniższa cena z 30 dni)
262.65 zł
309.00 zł(-15%) -
Edge AI is transforming the way computers interact with the real world, allowing IoT devices to make decisions using the 99% of sensor data that was previously discarded due to cost, bandwidth, or power limitations. With techniques like embedded machine learning, developers can capture human intu...(0,00 zł najniższa cena z 30 dni)
262.65 zł
309.00 zł(-15%) -
Why is it difficult for so many companies to get digital identity right? If you're still wrestling with even simple identity problems like modern website authentication, this practical book has the answers you need. Author Phil Windley provides conceptual frameworks to help you make sense of all ...(0,00 zł najniższa cena z 30 dni)
186.15 zł
219.00 zł(-15%) -
Python was recently ranked as today's most popular programming language on the TIOBE index, thanks to its broad applicability to design and prototyping to testing, deployment, and maintenance. With this updated fourth edition, you'll learn how to get the most out of Python, whether you're a profe...(0,00 zł najniższa cena z 30 dni)
296.65 zł
349.00 zł(-15%) -
With the accelerating speed of business and the increasing dependence on technology, companies today are significantly changing the way they build in-house business solutions. Many now use low-code and no code technologies to help them deal with specific issues, but that's just the beginning. Wit...
Building Solutions with the Microsoft Power Platform Building Solutions with the Microsoft Power Platform
(0,00 zł najniższa cena z 30 dni)262.65 zł
309.00 zł(-15%) -
Companies are scrambling to integrate AI into their systems and operations. But to build truly successful solutions, you need a firm grasp of the underlying mathematics. This accessible guide walks you through the math necessary to thrive in the AI field such as focusing on real-world application...(0,00 zł najniższa cena z 30 dni)
262.65 zł
309.00 zł(-15%) -
DevOps engineers, developers, and security engineers have ever-changing roles to play in today's cloud native world. In order to build secure and resilient applications, you have to be equipped with security knowledge. Enter security as code.In this book, authors BK Sarthak Das and Virginia Chu d...(0,00 zł najniższa cena z 30 dni)
186.15 zł
219.00 zł(-15%) -
With the increasing use of AI in high-stakes domains such as medicine, law, and defense, organizations spend a lot of time and money to make ML models trustworthy. Many books on the subject offer deep dives into theories and concepts. This guide provides a practical starting point to help develop...(0,00 zł najniższa cena z 30 dni)
262.65 zł
309.00 zł(-15%) -
Why are so many companies adopting GitOps for their DevOps and cloud native strategy? This reliable framework is quickly becoming the standard method for deploying apps to Kubernetes. With this practical, developer-oriented book, DevOps engineers, developers, IT architects, and SREs will learn th...(0,00 zł najniższa cena z 30 dni)
262.65 zł
309.00 zł(-15%) -
Learn the essentials of working with Flutter and Dart to build full stack applications that meet the needs of a cloud-driven world. Together, the Flutter open source UI software development kit and the Dart programming language for client development provide a unified solution to building applica...(0,00 zł najniższa cena z 30 dni)
220.15 zł
259.00 zł(-15%)
Dzieki opcji "Druk na żądanie" do sprzedaży wracają tytuły Grupy Helion, które cieszyły sie dużym zainteresowaniem, a których nakład został wyprzedany.
Dla naszych Czytelników wydrukowaliśmy dodatkową pulę egzemplarzy w technice druku cyfrowego.
Co powinieneś wiedzieć o usłudze "Druk na żądanie":
- usługa obejmuje tylko widoczną poniżej listę tytułów, którą na bieżąco aktualizujemy;
- cena książki może być wyższa od początkowej ceny detalicznej, co jest spowodowane kosztami druku cyfrowego (wyższymi niż koszty tradycyjnego druku offsetowego). Obowiązująca cena jest zawsze podawana na stronie WWW książki;
- zawartość książki wraz z dodatkami (płyta CD, DVD) odpowiada jej pierwotnemu wydaniu i jest w pełni komplementarna;
- usługa nie obejmuje książek w kolorze.
W przypadku usługi "Druk na żądanie" termin dostarczenia przesyłki może obejmować także czas potrzebny na dodruk (do 10 dni roboczych)
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.
Książka, którą chcesz zamówić pochodzi z końcówki nakładu. Oznacza to, że mogą się pojawić drobne defekty (otarcia, rysy, zagięcia).
Co powinieneś wiedzieć o usłudze "Końcówka nakładu":
- usługa obejmuje tylko książki oznaczone tagiem "Końcówka nakładu";
- wady o których mowa powyżej nie podlegają reklamacji;
Masz pytanie o konkretny tytuł? Napisz do nas: sklep[at]helion.pl.


Oceny i opinie klientów: Building Secure and Reliable Systems. Best Practices for Designing, Implementing, and Maintaining Systems Heather Adkins, Betsy Beyer, Paul Blankinship (0)
Weryfikacja opinii następuję na podstawie historii zamówień na koncie Użytkownika umieszczającego opinię. Użytkownik mógł otrzymać punkty za opublikowanie opinii uprawniające do uzyskania rabatu w ramach Programu Punktowego.