Ananta Companies A.I CyberSecurity Scoring
02/04/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for Ananta Companies in 2026.
No incidents recorded for Ananta Companies in 2026.
No incidents recorded for Ananta Companies in 2026.
Apparel & Fashion
MAS is an innovation driven company founded on a perfect blend of daring and visionary thinking. Focusing on fashion and lifestyle, we are one of Asia’s largest manufacturers of intimate apparel, sportswear, performance wear and swimwear and provide IT solutions to the apparel and footwear industry worldwide. MAS nurtures and drives a culture of excellence where over 114,000 global associates activate their full potential. Our identity, which goes beyond great products, is deeply embedded in community well-being and nurturing world-class teams.
BRFL is a vertically integrated textile company, engaged in the manufacture of a wide range of fabrics and garments from state of the art production facilities. Apart from being the largest Shirt manufacturer in India, we have successfully evolved into a multi-fiber manufacturing company producing fabrics such as Cotton, Polyester, Tencel, Modal, Lycra, Wool and various blends. Our yarn dyed fabric, printing techniques, finishing, processing, weaving, stitching are a mark of excellence making every piece of fabric perfect. With fabric manufacturing facilities of 100 million meters per annum, garment manufacturing facilities of 60 million pieces per annum, being expanded to 90 million pieces per annum and a strong employee base of around 38,000; BRFL is today one of the most sought after brands in the Indian as well as International fashion markets.
Q Collection, based in Singapore, is the parent company of the manufacturing entities collectively known as SQ Group in Bangladesh. As a leading global apparel manufacturing conglomerate, SQ is driven by a passion for innovation, sustainability, and excellence. With a rich heritage spanning 30 years, we operate through three dynamic business clusters: SQ Celsius (Knitwear), SQ Birichina (Lingerie & Activewear), and SQ Hues (Vertical Integration). Our commitment to sustainability is reflected in our LEED-certified facilities and ESG-focused operations. Our team of over 18,000 dedicated employees deliver high-quality products and services, guided by Q Collection's strategic vision of excellence and commitment to shaping the future of apparel manufacturing.
At BESTSELLER, we are more than 22,000 people in 38 different countries working for over 20 fashion brands such as ONLY, JACK & JONES, VERO MODA, NAME IT, SELECTED, VILA, PIECES, OBJECT, MAMALICIOUS, NOISY MAY and Y.A.S. We are a family-owned company with a strong foundation and values to build on, empowering us to pursue the ideas we believe in to take BESTSELLER forward. We are committed to diversity and provide equal opportunities for everyone, irrespective of sex, race, ethnicity, religion or belief, disability, age, sexual orientation or gender identity. We strive to create an empowering environment where people can thrive and develop. Our long-term business success is inextricably linked with respecting people and planetary boundaries. Our commitment to responsible operations extends beyond our own company and throughout our value chain. Our sustainability strategy, Fashion FWD, guides our actions towards our sustainability goals and sets the direction for the future of our company. Fairness, opportunities and a sense of responsibility is part of our vision in BESTSELLER. We treat each other as family, which means that we take each other’s differences into account, while creating an empowering environment where people can thrive and develop. We always put our family first and this is what unites us and makes us stronger together.
Latest updates, reports, and threat intel affecting the global network.
And deploy high-density, liquid-cooled AI infrastructure and neocloud services aligned with the country's data sovereignty goals.
Google Bengaluru Expansion News: Amid stricter H1-B visa rules, Alphabet leases 24 lakh sq ft office in Whitefield to house up to 25000...
Growing reliance on online infrastructure and tighter security standards are driving demand for digital certificate management among Indian...
In this exclusive interaction, Anant Deshpande, Regional VP of DigiCert, discusses the company's strategic roadmap for India as the nation's...
Over the coming years, structural shifts are set to reshape key sectors of the Indian economy, creating potential investment opportunities.
The minority stake sale will support AppZen's investments in agentic AI.
As the CISO and head of digital integrations at Adani Cement, he is responsible for leading comprehensive cybersecurity strategies and digital transformation...
Vishal Gupta, Bessemer's long-standing partner in India, paints a canvas that spans from D2C to cybersecurity.
Authentication bypass using an alternate path or channel vulnerability in N-able N-central allows Authentication Bypass. This issue affects N-central: through 2026.1.
Improper Verification of Cryptographic Signature in ueberauth guardian allows an unauthenticated attacker to revoke a victim's session with a forged token. Guardian.revoke/3 in lib/guardian.ex decodes the supplied token with peek/1, which performs no signature verification (it only base64-decodes the JWT header and payload). The resulting unverified claims are forwarded directly to the configured token module's revoke callback and the implementation's on_revoke callback, a state-mutating sink. The sibling operations refresh/2 and exchange/4 both call decode_and_verify first, so the signature is checked before anything acts on the claims; revoke/3 is the only state-mutating path that acts on claims without verifying the signature. An attacker who knows or guesses a victim's identifying claim values (jti, sub) can forge a JWT carrying those claims, sign it with an arbitrary key, and submit it to any endpoint that funnels a caller-supplied token into Guardian.revoke/3 (the standard logout / session-revocation pattern). When the token module mutates state keyed by the claims (whitelist deletion or blacklist insertion, for example a GuardianDb-style store), the victim's legitimate session is evicted. This is an unauthenticated session-revocation denial of service; the attacker never needs the signing secret. This issue affects guardian: from 1.0.0 before 2.4.1.
Allocation of Resources Without Limits or Throttling vulnerability in ueberauth guardian (Guardian.Permissions module) allows a denial of service via BEAM atom-table exhaustion. This vulnerability is associated with program file lib/guardian/permissions.ex and program routines 'Elixir.Guardian.Permissions':encode_permissions!/1, 'Elixir.Guardian.Permissions':encode_permissions_into_claims!/2, 'Elixir.Guardian.Permissions':do_encode_permissions!/2. The Guardian.Permissions mixin installs a public encode_permissions!/1 function on every module that does use Guardian.Permissions. For each key of the supplied map, encode_permissions!/1 calls String.to_atom(to_string(k)) before any validation runs. The integer-value clause of do_encode_permissions!/2 then short-circuits straight to encoding without validating the key against the configured permission set, so a key with an integer value is interned as a fresh atom with no exception raised. Atoms are never garbage collected and the BEAM atom table is a fixed-size resource (default roughly 1,048,576 entries), so each unique attacker-chosen key permanently consumes one slot. An attacker who can influence a permission map that reaches encode_permissions!/1 (for example a permissions map read from a request body and passed into token issuance via encode_permissions_into_claims!/2) can mint an unbounded number of atoms and exhaust the atom table, crashing the entire BEAM node and every service running on it. The sibling decode_permissions/1 is not affected because it skips keys absent from the configured permission set. This issue affects guardian: from 2.0.0 before 2.4.1.
Allocation of Resources Without Limits or Throttling in ueberauth guardian allows denial of service via unbounded atom creation from attacker-controlled binary input. Guardian.Permissions.AtomEncoding encodes permission scopes by passing arbitrary binaries to String.to_atom/1. When encode/3 in lib/guardian/permissions/atom_encoding.ex is called with a list, each binary entry is handled by the encode_value/3 binary clause, which calls String.to_atom(value) with no allow-list check. The perm_set argument (the application's small, finite set of legitimate permission names) is discarded, so any external string flows straight into atom creation. This encoder is selected with use Guardian.Permissions, encoding: Guardian.Permissions.AtomEncoding and reached through the imported encode/3 entry point. String.to_atom/1 creates a brand-new atom for every previously unseen binary, atoms are never garbage collected, and the BEAM atom table is fixed at roughly 1,048,576 entries by default. An application that funnels attacker-influenced permission scopes (from a request body, a JWT claim, or other external input) into encode/3 therefore mints one permanent atom per distinct value. A modest stream of varied, unauthenticated input permanently consumes the atom table and crashes the BEAM node with system_limit, taking down every application running on it. The default encoder is Guardian.Permissions.BitwiseEncoding, which is not affected. This issue affects guardian: from 2.0.0 before 2.4.1.
Allocation of Resources Without Limits or Throttling in ueberauth guardian allows denial of service via unbounded atom creation from attacker-influenced binary input. Guardian.Plug.Keys derives connection and session namespace keys by passing arbitrary binaries to String.to_atom/1. base_key/1 in lib/guardian/plug/keys.ex converts any binary into the atom :"guardian_<input>", and the derived helpers claims_key/1, resource_key/1, and token_key/1 create a second atom on top of that. key_from_other/1 likewise converts a regex-captured binary through String.to_atom/1. The public specs advertise String.t() as a valid argument, so passing a string is documented usage, and higher-level entry points such as Guardian.Plug.current_token(conn, key: key) thread the caller-supplied key straight into these functions. String.to_atom/1 creates a brand-new atom for every previously unseen binary, atoms are never garbage collected, and the BEAM atom table is fixed at roughly 1,048,576 entries by default. An application that routes attacker-influenced data (a tenant identifier, header, or other request input) into a Guardian key therefore mints one permanent atom per distinct value. A modest stream of varied, unauthenticated input permanently consumes the atom table and crashes the BEAM node, taking down every application running on it. This issue affects guardian: from 0.1.0 before 2.4.1.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.