Contact

Mobile Security Authority serves as a national reference provider network for the mobile device security sector, covering service providers, regulatory frameworks, technical standards, and professional categories. This page describes how to reach the editorial and administrative office, what information to include in a message, and the response protocols that govern this reference property.

What to include in your message

Effective communication with the editorial office depends on the specificity of the inquiry. Messages that lack identifying context — such as the specific page URL in question, the nature of the issue, or the professional role of the sender — routinely result in delayed or incomplete responses.

Structured inquiries should include the following components:

  1. Page or section reference — the full URL or descriptive title of the page the inquiry concerns (e.g., Mobile Security Providers or How to Use This Mobile Security Resource)
  2. Inquiry category — editorial correction, provider submission, factual dispute, regulatory update, or administrative matter
  3. Supporting documentation — for factual disputes or regulatory updates, a reference to the named public source (e.g., a specific NIST Special Publication number, a statute citation such as 44 U.S.C. § 3551, or a named agency advisory)
  4. Organization or affiliation — the sender's professional role or institutional affiliation, where relevant to the inquiry
  5. Contact preference — whether a written response or scheduled callback is preferred

Inquiries referencing mobile device security standards should identify the specific framework at issue. The National Institute of Standards and Technology (NIST) publishes NIST SP 800-124 Rev. 2 as the primary federal guidance document for enterprise mobile device management; the Federal Information Security Modernization Act, codified at 44 U.S.C. § 3551 et seq., governs federal agency obligations in this area. Citing the specific revision or section relevant to the inquiry accelerates editorial review.

Provider-related inquiries — submissions, updates, or removal requests — should distinguish between 3 distinct request types: new entry submission, amendment to an existing provider, or delisting. Each follows a separate review path and carries a different processing timeline.

Response expectations

The editorial office processes incoming messages according to inquiry category and documentation completeness. Factual correction requests supported by a named public source receive priority handling. Undocumented assertions regarding regulatory compliance or technical standards are not actionable without a traceable citation to an authoritative body such as NIST, the Cybersecurity and Infrastructure Security Agency (CISA), the Federal Trade Commission (FTC), or a state-level regulatory authority.

Standard response windows by category:

Incomplete messages — those missing a page reference, category identification, or supporting documentation — are held pending follow-up rather than forwarded for editorial review. This distinction between held and active status affects the effective response timeline by up to 7 additional business days.

Regulatory inquiries referencing the FTC Act (15 U.S.C. § 45) or sector-specific mobile data frameworks such as HIPAA's Security Rule (45 C.F.R. Part 164) should identify the applicable rule and the specific provision in question. Generic references to "data privacy law" or "cybersecurity regulation" do not provide sufficient context for editorial review.

Additional contact options

The primary contact method for this property is the administrative email address associated with the editorial office. For matters requiring documented correspondence, email provides a complete audit trail and is the preferred channel for provider submissions and factual disputes.

For time-sensitive matters involving a named public agency action — for example, a CISA advisory, an FTC enforcement action, or a NIST publication that directly affects provider network content — the inquiry should be marked with the agency name and advisory identifier in the subject line. This categorization separates regulatory-trigger messages from standard editorial queues.

The page describes the editorial standards and inclusion criteria that govern this provider network, which provides relevant context before submitting a provider inquiry. Reviewing that page before contacting the office reduces the likelihood of a submission being returned for clarification.

How to reach this office

Administrative and editorial contact:
Email: [email protected]

This address handles editorial corrections, provider submissions, regulatory update notifications, and general administrative correspondence related to Mobile Security Authority. All communications should reference the specific page or section at issue and include the applicable inquiry category as described in the section above.

The provider network operates under the editorial and administrative umbrella of nationalcyberauthority.com, which serves as the parent reference domain for national-scope cybersecurity provider network content. Matters pertaining to the broader network architecture or cross-domain editorial standards should be directed to that domain's administrative contact rather than to this property's editorial address.

Report a Data Error or Correction

Found incorrect information, an outdated fact, or a broken link? Use the form below.

Interested in becoming a verified provider?

[email protected]

Include your business name, location, and services offered.

 ·   · 

References