मुखपृष्ठ/विषय/उद्यम सुरक्षा

उद्यम सुरक्षा

उद्यम सुरक्षा

व्यावसायिक लचीलापन उन सेवाओं से शुरू होता है जिनके रुकने से काम प्रभावित होता है। निर्भरताएँ, ज़िम्मेदार व्यक्ति, महत्त्वपूर्ण खाते और प्रदाता पहचानें; वैकल्पिक संचार माध्यम से बहाली का अभ्यास करें।

SOCCloudResilience
संध्या के समय खाली दूरस्थ दूरसंचार रिले केंद्र
AI से निर्मित संपादकीय चित्रण

इस विषय में

Small business · CISO · SOC · Cloud · Supply chain · Continuity · Third-party risk

व्यावहारिक मार्गदर्शिकाएँ

Organise enterprise security in six steps

Where should enterprise security begin? With an essential service, its dependencies and the consequence of disruption. This guide connects six management decisions to operational evidence: named owners, known assets, restricted access, assessed suppliers, exercised recovery and explained metrics. The output is a prioritised plan that business owners can understand and technical teams can verify after remediation.

मार्गदर्शिका पढ़ें EN

समाचार निगरानी

सभी अंतरराष्ट्रीय समाचार →

सहेजी गई सुर्खियाँ · अद्यतन अनुपलब्ध · अंतिम सफल प्राप्ति : 22 अक्तू॰ 2026, 9:25 pm

संदर्भ: डेटा, उपयोग और सीमाएँ

दस्तावेज़ जाँच की तारीख .

इस संस्करण में विस्तृत संदर्भ टिप्पणियाँ अंग्रेज़ी में उपलब्ध हैं।

संदर्भ: डेटा, उपयोग और सीमाएँ
स्रोत और उद्देश्यसत्यापित डेटा या मानकउपयोग कैसे करेंध्यान में रखने योग्य सीमा
NIST · Cybersecurity Framework

Structure the outcomes expected from a cybersecurity programme.

 CSF 2.0 has six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe a single way to achieve outcomes. Describe current and target profiles with evidence, gaps and owners. Connect each priority to the services it helps protect.

विधि को विस्तार से पढ़ें →

 Mapping to the framework is neither certification nor proof that every control works.
NIST · SP 800-61 Rev. 3

Prepare incident response within cybersecurity risk management.

 Revision 3 was published in April 2025 and supersedes Revision 2. It is a CSF 2.0 Community Profile. Rehearse containment decisions, evidence preservation, communication and recovery. Compare planned actions with evidence produced during the exercise.

विधि को विस्तार से पढ़ें →

 Reading the guide does not validate a local plan. Contacts, emergency access and dependencies need local testing.
NIST · Privacy Framework

Examine risks to people arising from data processing.

 The Privacy Framework is a voluntary privacy risk-management tool. It is distinct from a universal legal compliance checklist. Describe actual processing: data, purposes, recipients, access and retention. Compare documents, settings and deletion or retrieval tests.

विधि को विस्तार से पढ़ें →

 Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination.

ईमेल सुरक्षा: पहचान, एलाइनमेंट और परिवहन

इस संस्करण में विस्तृत संदर्भ टिप्पणियाँ अंग्रेज़ी में उपलब्ध हैं।

Business email: separate identity and availability

A message can pass SPF or DKIM for a third-party domain while failing From alignment. Document each provider and use before interpreting a global indicator.

  • Separate critical alerts, human correspondence and campaigns.
  • Associate authentication results with the domain actually evaluated.
  • Correlate DMARC reports with TLS transport incidents; they observe different phenomena.

Open the comparison and DMARC simulator →

References and status checked on · SPF · RFC 7208 DKIM · RFC 6376 DMARC · RFC 9989

Retry-After: प्रतीक्षा, बजट और पुनःप्रयास

इस संस्करण में विस्तृत संदर्भ टिप्पणियाँ अंग्रेज़ी में उपलब्ध हैं।

Retries can amplify a dependency outage

Deadlines and attempt limits need to span integration layers. Each uncoordinated retry layer can increase downstream work.

  • Identify the client, SDK, proxy and queue that can each retry.
  • Compare server wait, local delay and remaining budget before retrying.
  • Separate repeatable reads from writes whose effects need reconciliation first.

Explore Retry-After and the retry model →

References reviewed · RFC 9110 · §9.2.2, §10.2.3 · RFC 6585 · §4 · AWS

Webhooks: हस्ताक्षर और पुनःप्रेषण

इस संस्करण में विस्तृत संदर्भ टिप्पणियाँ अंग्रेज़ी में उपलब्ध हैं।

API recovery and webhook recovery follow different contracts

For incoming notifications, track the event, transport attempt and business effect separately. A signature authenticates a message; it is not an idempotency key.

  • Retain required raw bytes and authenticate each new attempt.
  • Plan provider-specific recovery: Stripe can retry automatically; GitHub does not automatically redeliver failures.
  • Test lost responses, concurrency and post-outage reconciliation.

See webhook signatures, digests and the ten cases →

Sources reviewed on · Stripe · Webhooks · Stripe · Manage webhook endpoints · GitHub · Validating webhook deliveries · GitHub · Best practices for using webhooks · GitHub · Handling failed webhook deliveries

PDF: संपादन और साझाकरण

इस संस्करण में विस्तृत संदर्भ टिप्पणियाँ अंग्रेज़ी में उपलब्ध हैं।

Document review covers both file and sharing

A digital-trust dossier must show which checks covered which copy. A result grid replaces neither content inspection nor checks on access and accessible versions.

  • Define confidentiality scope and information needed by the recipient.
  • Retain results and unperformed checks without turning them into a reassuring score.
  • Match the approved copy to the file actually released.

See surfaces and the pre-sharing review matrix →

Sources reviewed on · Adobe · Redacting and sanitizing PDFs · Adobe · Redact sensitive content · Adobe · Sanitize PDFs · ICO · Avoid accidental breaches when redacting · ICO · Hidden information in documents · Microsoft · Document Inspector